15:21:00 GMT <Guest53845> Hey all.
15:21:58 GMT <Guest53845> I was looking into internal workings of redis pub/sub but I couldn't find any blogs that could explain its working.
15:22:02 GMT <Guest53845> I wanted to know if I could get an event every time someone publishes a message?
15:22:15 GMT <Guest53845> I'm currently doing it with a infinite for loop.
16:57:04 GMT <__unempl1yedbot> given a sorted set, is there a way to retrieve a member and its score? in the redis docs, i only see ZRANGE* commands.
16:58:44 GMT <minus> yes, ZRANGEBYSCORE
16:58:54 GMT <minus> be aware that it's a floating point number
17:03:16 GMT <__unempl1yedbot> but i only want a specific member and i do not know its score
17:03:23 GMT <__unempl1yedbot> i only know the member name
17:06:10 GMT <minus> you want to know its score?
17:06:32 GMT <__unempl1yedbot> yes
17:07:23 GMT <__unempl1yedbot> i can only think of using a combination fo ZRANK key member, and then use the result in ZRANGE key rank rank
17:08:23 GMT <minus> maybe use a hash instead then
17:10:35 GMT <__unempl1yedbot> ok, i will investigate this. thanks minus.
17:11:48 GMT <__unempl1yedbot> i wonder why they don't implement a command to get a member. its functionality is already in ZINCRBY
17:17:50 GMT <badboy_> https://redis.io/commands/zscore
17:18:27 GMT <minus> uhm, right
17:18:36 GMT <minus> __unempl1yedbot: you're blind. and so am i
17:22:13 GMT <__unempl1yedbot> lol, yes i am ;[
17:22:18 GMT <__unempl1yedbot> thanks badboy!
17:22:43 GMT <__unempl1yedbot> *sighs* not sure how i missed this.
17:24:19 GMT <badboy_> you are welcome
20:42:42 GMT <roskowski101> idea for redis extension to the keyspace events - add the ability to get subscription add/drop events
20:43:28 GMT <roskowski101> so you get a event when someone subscribes to key, or to a key matching your pattern.
20:43:49 GMT <roskowski101> looks like a very easy extension.  Am writing it locally, should I persue it as something to push upstream or keep local?
20:43:51 GMT <minus> it's not really a keyspace event though
20:44:14 GMT <minus> just like clients connecting/disconnecting isn't one (but might be nice too?)
20:44:42 GMT <roskowski101> agreed on both points.
20:45:47 GMT <roskowski101> I am using subscriptions to indicate "interest" in a key, so the "server" end can know when a key is needed.  Clients look for key in cache and subscribe to keyspace event with same name.
20:46:00 GMT <roskowski101> server can see subscription, and fill in the key.
20:46:24 GMT <roskowski101> results in keyspace event, client pulls the key and done.  Seemless, coherent distributed caching.
20:47:18 GMT <roskowski101> anyway - really just probing for interest in pushing this upstream, as it means somewhat more care in coding...
20:49:35 GMT <roskowski101> the subscription effectively becomes a "connection" monitor for clients interest in a key.