Pankaj Tandon wrote:
> So if I prefer to build a thread in my client app that goes out and
> 'asynchronously' invokes an eJB, I would be doing work in the client which
> shd be handled by the eJB. Is that the 'con'? It would seem to be a minor
> one, given Java's support for multithreading. Or am I oversimplifying?
You are right, when thinking only of a client client. However think also of a
server client, eg your EJB server as client to my EJB server.
1. No threads so you have to make the call synchronously
2. You cannot passivate your beans while waiting for my overloaded
server to respond so your server gets clogged up and won't scale.
Ian McCallion
CICS Business Unit
IBM Hursley
[EMAIL PROTECTED]
Tel: ++44-1962-818065
Fax: ++44-1962-818069
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
