JRedis 2.0 API - RFC

5 views
Skip to first unread message

Joubin Houshyar

unread,
Jun 29, 2010, 7:12:18 PM6/29/10
to JRedis
Hi all,

This is quite wip but its the direction that the JRedis 2.0 is
heading, so wanted to give you all a heads up and get your feedback
before committing to the new API.

1- It will break your existing code.
2- It will allow for supporting all the new interaction semantics and
is open-ended (meaning after this, far less pain in API upgrades).

The basic sketch of the API:
http://gist.github.com/457961

Usage example:
http://gist.github.com/457960

Timeline:

Please comment on this change before we commit to it (eta ~ 1 week).

Thanks.

/R

Joubin Houshyar

unread,
Jun 29, 2010, 7:28:34 PM6/29/10
to JRedis
Note on alternative:

I am sensitive to the issue of backward compatibility. We can
sacrifice a bit of clarity towards that end and maintain existing
JRedis 1.0 API fully defined in the new 2.0. Wasn't entirely happy
with this given that it will give rise to a bit of redundancy in the
sync/async API, but any existing code should still be functional.
Perhaps this is the best way to go.

Also note that MONITOR support is the lowest priority interface. I
see the priorities as Admin (trivial), Tx, and Topic.

/R
Reply all
Reply to author
Forward
0 new messages