You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.
Is it possible to consume redis messages within same order as they were published? E.g. see code below:
def __init__(self):
self.async_redis_publisher = tornadoredis.Client(port=TORNADO_REDIS_PORT)
self.async_redis = tornadoredis.Client(port=TORNADO_REDIS_PORT)
@engine
def listen(self, channels):
yield Task(self.async_redis.subscribe, channels)
self.async_redis.listen(self.pub_sub_message)
def pub_sub_message(self, message):
print(current_time, message)
# code below represents 2 different *web socket messages* within same thread and same insntance of class
def on_ws_message(self):
self.async_redis_publisher.publish('1', 'message1') # also prints time to be sure about order
# some timeout or e.g. another request
self.async_redis_publisher.publish('1', 'message2') # also prints time to be sure about order
I have a stackoverflow question here.
Is it possible to consume redis messages within same order as they were published? E.g. see code below:
redis-cli: monitor:
The text was updated successfully, but these errors were encountered: