>> Costin, >> >> that point of view is really interesting. What about separating the >> distribution part from the integration part of a integrated solution. >> That would user's give the option to use the "transparent session >> replication" or to use "explicit object replication services". >> The former would ease their live with the drawback of >missing transaction >> support, the latter would give the app-developer all control over it. > >More important is separating the implementation of the 'distribution' >part as a stand-alone module. > >I'm absolutely -1 on putting this in the same space with the >main tomcat4 >- it's already a huge mess and adding this much complexity is >going to make >things worse.
May be a good candidate for jakarta-commons, since it could be used for example in Avalon. I'm not even sure that a Distributed Stuff Management is even Servlet Engine Specific, it fit more on EJB repository land. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
