Hi Guys, This seems to be a very good proposal and +1 to go ahead. I am +1 *not* to cluster operation contexts and message contexts since the overhead will be enormous and we would probably loose the advantage of the clustering! Anyway have you guys thought about the following issues ? (I'm not sure whether these details are already discussed or not. If so bear with me :))
1. How would the replication happen ? How much resources would be used for clustering depends partly on the mechanism we select to transfer the state - and of course this brings up the issue whether the contexts are serializable or not (Since our contexts are 'unrestricted' service authors can put all sorts of junk there) ! As Rajith suggested we can use something like JGroups or Tribes underneath or do we go for a relevant WS specification ? I believe there was an idea of using RSS for doing this! 2. How can you deploy a service in the cluster ? Since we are using a remote repository the ability to just drop in an archive to the remote repo would not suffice (I suppose the lst file needs to be modified too). This might be problematic if we have a hot deployment mechanism. I'll come up with more comments when I get enough time to think through the matters :) -- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
