Re: [infinispan-dev] Hot Rod - pt3

>> - No events. I used events, that is asynchronous messages originating >> from the server when certain conditions are met, to notify clients >> that data was written to the server. This was mostly driven by the >> need to notify an L1 cache of a write to the cache server. It would >> be good to allow for this usage in this protocol. Note that this is >> another case where the op code is useful to have as part of the >> message. > > Isn't this expensive? Doesn't this mean the server > has to fire off messages to each and every connected client, > whether the clients are interested in these messages or > not? Not necessarily. There are a number of options. It wouldn't be difficult to allow the clients to register for the events, and then only send them to the interested clients. The events can be sent asynchronously (a separate thread), thus they won't delay the response to a write. Piratically speaking, they aren't that expensive.