Hi Alex,
Yes, as you have mentioned to deploy Sandesha in a cluster it needs a
persistance storage and we don't have it in Sandesha1. So if you can
implement the SandeshaDatabaseDAO interface then you can get the
persistence behavior in Sandesha1.
Sandesha2 already has a persistence layer and we have some issues in
publishing it to the public domain due to some licensing issues and will do
it soon. In both cases we have Sender and Invoker's are stateless so will be
able to use them in a cluster.
It will be really nice if you can give it a try and let us know.
Thanks,
Jaliya
----- Original Message -----
From: "Alex Horwitz" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, March 24, 2006 9:01 AM
Subject: Sandesha in a Cluster
Hello all:
Has anyone had experience deploying Axis/Sandesha in a Cluster? After
looking briefly at the server-side architecture, it almost appears that a
single, persistent queue shared among all Sandesha web applications in a
cluster might be a simple architecture that avoids the need for sticky
sessions or session attributes, as the server components (sender, invoker)
are event-driven and stateless.
Any suggestions / advice on how to approach this problem would be greatly
appreciated.
Cheers,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
