I too have to agree, soap would be way to slow. And again, the multicast
messages do not have to involve the web server, only between the servlet
engines and between the app servers in a cluster.
are you planning on implementing the same features/restrictions as Weblogic.
in other words, replicate the entire HTTP session, create replica aware
stubs for the home interfaces.
but once your client holds a connection to a ejb object it is considered
pinned, and it's state will not get replicated unless it is a read only data
bean.
because it would be a nice feature, if the fail over was transparent even
once you hold a reference to an EJB object.
I'd like to help out, any design docs or anything tangible I can dig in to?
best regards,
Filip
----- Original Message -----
From: "Peter Braswell" <[EMAIL PROTECTED]>
To: "jBoss Developer" <[EMAIL PROTECTED]>
Sent: Thursday, December 21, 2000 8:10 AM
Subject: Re: [jBoss-Dev] using Jini for clustering
Rickard... very agreeable today.. Merry Xmas!
cheers (and happy holidays)
peter
p.s. Wouldn't mind being involved with clustering if
you need a hand...
--- Rickard �berg <[EMAIL PROTECTED]> wrote:
> Hi!
>
> Peter Braswell wrote:
> > Wouldn't this solution be slow?
>
> Yes.
>
> > Not intimate with
> > SOAP but would the addition of tags bloat the
> volume
> > of data shared between servers..
>
> Yes.
>
> > JINI seems like a pretty cool idea...
>
> Yes.
>
> :-)
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
>
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
