The current HA proxy logic is embedded in the protocol specific proxy. That logic is what we need: - A list of targets encapsulated in a protocol indepdent view (currently org.jboss.invocation.Invoker) - A policy for selecting the next target - A mechanism for propagating info between the client and server to update the list of active targets xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
________________________________ From: [EMAIL PROTECTED] on behalf of Ivelin Ivanov Sent: Mon 12/22/2003 9:13 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Re: HA JMS - singleton load balancing policy Can you enumerate the key features of a clustered interceptor? --- Sacha Labourey <[EMAIL PROTECTED]> wrote: > As part of 4.0, we have to replace the smart proxies > with clustered > interceptors, we could reuse them then. > > > -----Original Message----- > > From: > [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > On > > Behalf Of Ivelin Ivanov > > Sent: dimanche, 21. d�cembre 2003 18:05 > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-dev] Re: HA JMS - singleton > load balancing policy > > > > > > Yes, this is how it works now. > > The client side of the HAIL uses the singleton > > notifications, which in turn use the DRM. > > The question is how to implement the client stub > so > > that it does not have to be part of the cluster. > > > > The smart RMI stubs take care of communicating > with > > the back end to receive regular snapshots of the > > cluster view. There has to be additinal info about > the > > current singleton server. As Scott mentioned this > can > > be probably done as an extension to one of the > load > > balncing policies. > > > > However UIL2 does not use the smart RMI stubs. How > to > > merge them? Just use the RMI stuff for HAIL and > don't > > worry about UIL2 for now? > > > > Is the existing remoting at a stage that can > replace > > UIL2 without any loss of benefits ? I am not > familiar > > with it yet. > > > > Ivelin
<<winmail.dat>>
