Yep yep, I agree, people do chase those picoseconds sometimes. ;) In this case, there really is a performance issue to be addressed with high-volume sites regarding EJB calls. Apparently the creators of the EJB 1.1 spec didn't think about that when they were locked behind closed doors and throwing specifications out through the mail slot. :)
peace, Joe > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 08, 2002 3:11 PM > To: Struts Users Mailing List > Subject: RE: [OT] Container Wars - Resin and sessions > > > > > > > > > Joe - Thanks for explaining. I've seen so many people make > decisions based > on 'potential' performance problems that never occur that I > always question > the need. Sometimes there's really a difference, other times it's just > "running from ghosts"! > > I appreciate your insight - > > Kevin > > > > > > Why is having an internal connector better than simply > > > creating a JNDI/ > > > initial context on your own? > > > > > Because w/ the internal connector, all EJB calls are > in-VM. With a > created JNDI context, all EJB calls go on the > > > network call stack unless you are using EJB 2.0 local > interfaces AFAIK. > > > > >Is the speed that much better? > > > > yes. esp. on windows machines where the network call stack > implementation is not so speedy. > > > > >It's not > > > really too hard to simple set your jndi.properties directly > > > and connect > > > that way. > > > Not trying to put your decision down, just wondering if I've > > > missed something... > > > > > > Seems like choosing the best container would outweigh this > > > connectivity > > > issue... > > > > Not if choosing the "best" container results in a > substantially slower > application....which is very possible when > > the EJB calls start "bottle-necking" on the call stack during high > traffic...with low traffic, you probably > > wouldn't notice a difference. > > > > > -------------------------------------------------------------- > ------------- > This e-mail message (including attachments, if any) is > intended for the use > of the individual or entity to which it is addressed and may contain > information that is privileged, proprietary , confidential > and exempt from > disclosure. If you are not the intended recipient, you are > notified that > any dissemination, distribution or copying of this communication is > strictly prohibited. If you have received this communication > in error, > please notify the sender and erase this e-mail message immediately. > -------------------------------------------------------------- > ------------- > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
