1 Reply Latest reply on Sep 9, 2010 5:32 AM by galder.zamarreno

    A question regard Hot Rod

    yelin666

      I got couple questions regard Hot Rod:

      1. I read the “Using Hot Rod Server” page at http://community.jboss.org/wiki/UsingHotRodServer. In the paragraph under “Starting an Infinispan Hot Rod Server”, it has something like “Since Hot Rod clients can potentially talk to different cache instances using the cache name parameter, Hot Rod server does not attempt to start any particular cache on startup. Instead, cache instances will be started the first time a request is send to them.” And under “Predefining Hot Rod Caches”, there is something like “In order to provide a more consistent experience when interacting with Hot Rod servers and avoid issues related to lazily started cache instances, on startup, Hot Rod server starts all defined caches in the Infinispan configuration file including the default cache.” Those two descriptions seem contradict each other. So what’s the actual behaviors? Is there a configuration parameter to turn on/off this?
      2. At the client side, I looked at the RemoteCache API, and the description for addListener(Object listener), and it says “Operation might be supported for smart clients that will be able to register for topology changes.” I am wondering if it supports registering for cache entry updates at the server side? In some of our use cases, we may want to keep a partition of the data up-to-date on the local node for high performance read.
        • 1. Re: A question regard Hot Rod
          galder.zamarreno

          Re 1. Indeed, that's a contradiction that I'll fix asap. The way Hot Rod works is: "In order to provide a more consistent experience when interacting with Hot Rod servers and avoid issues related to lazily started cache instances, on startup, Hot Rod server starts all defined caches in the Infinispan configuration file including the default cache.". This behaivour cannot be configured.

           

          Re 2. No, clients can not yet be notified of cache entry updates. This on the road map though: https://jira.jboss.org/browse/ISPN-374