<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 10 Mar 2010, at 18:21, Galder Zamarreno wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Wed, 10 Mar 2010 14:08:23 +0100, Mircea Markus <br><<a href="mailto:mircea.markus@jboss.com">mircea.markus@jboss.com</a>> wrote:<br><br><blockquote type="cite">Hi Galder,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Here are some thoughts I have about how the hotrod client performs <br></blockquote><blockquote type="cite">initial connection to the HR servers:<br></blockquote><blockquote type="cite">A list of servers is statically configured so that the client can <br></blockquote><blockquote type="cite">connect to any of them<br></blockquote><blockquote type="cite"> 1. client will ping each configured server until it finds <br></blockquote><blockquote type="cite">one that is up and running<br></blockquote><blockquote type="cite"> 2. at this point it will stop(i.e. not query other <br></blockquote><blockquote type="cite">statically configured servers) and query this server for the cluster <br></blockquote><blockquote type="cite">topology<br></blockquote><br>The idea was that rather than querying for the cluster topology, the <br>client would register for notification it's interested in. From the wiki:<br><br>"Before any the server can send any notifications, clients need to <br>register and indicate which events they're interested in. To do that, they <br>have to send a request like this:<br><br>[request header][events]"<br><br>So, if a client was interested in topology change notifications, it would <br>tell the server accordingly.<br></div></blockquote><span class="Apple-style-span" style="font-family: 'Lucida Grande'; ">Isn't the event handling optional? if so, some clients (ones that do not implement event handling) would not be able to get the view?</span><br><blockquote type="cite"><div><br><blockquote type="cite"> 3. a a response to this query, the server informs the <br></blockquote><blockquote type="cite">client about hotrod cluster topology (which might be different than <br></blockquote><blockquote type="cite">infinispan cluster, right?)<br></blockquote><br>Although not specified in the wiki, I would assume that once you register <br>with the server, the server would push the current topology, no need for <br>further requests from client.<br><br><blockquote type="cite"> 4. based on this information client builds a pool of <br></blockquote><blockquote type="cite">connections to the servers<br></blockquote><blockquote type="cite"> 5. client register itself as cluster formation listener, <br></blockquote><blockquote type="cite">and update the list of active servers whenever the topology changes<br></blockquote><blockquote type="cite">(cluster formation might not be the best name for this listener as it <br></blockquote><blockquote type="cite">only refers to the time when cluster is formed, what about cluster <br></blockquote><blockquote type="cite">topology listener?)<br></blockquote><br>You'd still need a listener like the one you mention based on the <br>information received from the server(s).<br><br><blockquote type="cite">How does this sound to you?<br></blockquote><blockquote type="cite"></snip><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite">Mircea<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">infinispan-dev mailing list<br></blockquote><blockquote type="cite"><a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br></blockquote><blockquote type="cite"><a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br></blockquote><br><br>-- <br>Galder Zamarreņo<br>Sr. Software Engineer<br>Infinispan, JBoss Cache<br><br>_______________________________________________<br>infinispan-dev mailing list<br><a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/infinispan-dev</div></blockquote></div><br></body></html>