@tomdz 
You're right.
byte[] may be better to store cursor internally while both byte[] and String are compatible and Jedis get back response to byte[].
I'll fix this.

But I'm not sure about "cursorAsBytes" and "cursorAsString" because it would break compatibility.
We already expose getCursor() method for default and currently it's for Jedis, not BinaryJedis.
(Actually it's for both Jedis and BinaryJedis when cursor is integer.)

We may discuss again to naming getCursor()'s binary version, not modifying getCursor() returns String.
Or maintain three methods. (getCursor(), getCursorAsBytes(), getCursorAsString() )

@tomdz @xetorthio @marcosnils I'd love to hear your thought. Thanks!