--- Geoff Howard <[EMAIL PROTECTED]> schrieb: > > So far, every time I hear someone talk about using > EJB's and cocoon, the > topic gets bundled with deploying cocoon in the > appserver itself, which pegs > you to one front end machine and causes all of your > display logic (cocoon) > to run on the same disks and cpus as your ejb logic. As my little newbie soul sees it, that's not such a problem, because good application server allows to get rid of really resource-intensive EJBs or other components alone by distributing it elsewhere than on the machine running Cocoon.
> Is no one using EJB's > on a remote (conceptually remote, even if it's on > the same machine for now) > server from within cocoon? Seems to me that a > powerful set up is That was my initial proposal - accessing remote J2EE components from Cocoon - but it seems that reality has to deal with extended exception handling of all those possible errors coming from J2EE and that's why yet another link in the chain (incrementally handling the errors) should be established in between, to redirect requests avoiding Cocoon to implement complicated logic. > Of course the EJBServer and database can be > clustered too, but you'd need a > pretty whopping load before that would be necessary. That's exactly what I'm interested in. Taking lightweight, just Tomcat-based Cocoon with direct connection to DB has to be tested and benchmarked regarding concurrent user requests. If it fails for possible traffic on public site, then the J2EE should help out, because most bottlenecks are probably in business logic, after optimizing the technology. Are there sites or users doing these benchmarks available anywhere? Hoping to clear this issue, Peter. __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
