I would reccomend hivemind in this case. Because it makes working with threads "magical" as far as services are concerned. Spring doesn't handle this model nearly as well as hivemind.
On 3/29/06, Andrew Pym <[EMAIL PROTECTED]> wrote: > > I was speaking to an infrastructure person the other day about a badly > written EJB based application. > > For banter, I made some comments about tapestry/hivemind and spring. > > The main app server used at the company we are working at is WebLogic. > > The infrastructure guy complained about spring being single threaded and > had issues scaling horizonatally into clusters. > > Can someone enlighten me > > Is this a WebLogic issue with Spring? > A lack of knowledge about how to configure Spring? > Does the use of hivemind get around the single threaded spring issue, > since hivemind is a multi threaded registry/service model? > > What is the best setup to get horizontal scaling with Tapestry/hivemind? > What about if I have an app that includes Tapestry, hivemind and spring? > Can this be achieved with Jetty, Tomcat or Weblogic? > > > Regards > > Andrew > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://opennotion.com
