From 84973bcd5298838ec64efd87bed696d5a79abf8b Mon Sep 17 00:00:00 2001 From: Costin Leau Date: Tue, 18 Jan 2011 22:22:05 +0200 Subject: [PATCH] DATAKV-22 + add minor doc improvement --- src/docbkx/reference/redis-messaging.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/docbkx/reference/redis-messaging.xml b/src/docbkx/reference/redis-messaging.xml index a8b53c2dc..1ab6b5bc4 100644 --- a/src/docbkx/reference/redis-messaging.xml +++ b/src/docbkx/reference/redis-messaging.xml @@ -60,7 +60,8 @@ template.publish("hello!", "world");]]> Subscribing commands are synchronized and thus blocking. That is, calling subscribe on a connection will cause the current thread to block as it will start waiting for messages - the thread will be released only if the subscription is canceled, that is an additional thread invokes unsubscribe respectively pUnsubscribe - on the same connection. + on the same connection. See message listener container below + for a solution to these problem. As mentioned above, one subscribed a connection starts waiting for messages - no other commands can be invoked on it except for adding new subscriptions or modifying/canceling the existing ones, that is invoking anything else then subscribe,