From 678e3148be3f38f3f7aa0a7f6d424ccf38e9c64d Mon Sep 17 00:00:00 2001 From: Costin Leau Date: Tue, 18 Jan 2011 20:42:24 +0200 Subject: [PATCH] DATAKV-22 + add some docs improvements --- src/docbkx/reference/redis-messaging.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/docbkx/reference/redis-messaging.xml b/src/docbkx/reference/redis-messaging.xml index bd0fd44a7..28fc9b7c1 100644 --- a/src/docbkx/reference/redis-messaging.xml +++ b/src/docbkx/reference/redis-messaging.xml @@ -81,11 +81,11 @@ template.publish("hello!", "world");]]> Message Listener Containers Due to its blocking nature, low-level subscription is not attractive as it requires connection and thread management for every single - listener. To alleviate this problem, Spring Data offers RedisListenerContainer which does all the heavy lifting + listener. To alleviate this problem, Spring Data offers RedisMessageListenerContainer which does all the heavy lifting on behalf of the user - users familiar with EJB and JMS should find the concepts familiar as it is designed as close as possible to the support in Spring Framework and its message-driven POJOs (MDPs) - RedisListenerContainer acts as a message listener container; it is used to receive messages from a + RedisMessageListenerContainer acts as a message listener container; it is used to receive messages from a Redis channel and drive the MessageListener that are injected into it. The listener container is responsible for all threading of message reception and dispatches into the listener for processing. A message @@ -97,7 +97,7 @@ template.publish("hello!", "world");]]> boilerplate Redis infrastructure concerns to the framework. - Further more, to minimize the application footprint, RedisListenerContainer performs allows one connection and one thread + Further more, to minimize the application footprint, RedisMessageListenerContainer performs allows one connection and one thread to be shared by multiple listeners even though they do not share a subscription. Thus no matter how many listeners or channels an application tracks, the runtime cost will remain the same through out its lifetime. Moreover, the container allows runtime configuration changes so one can add or remove listeners while an application is running without the need for restart. Additionally, the container uses a lazy subscription approach, using a