You don't. The container will do thread management and connection
pooling and load balancing for you.
If you want async type stuff in your beans, then use JMS.
-- Aravind
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Matthew T.
> Machczynski
> Sent: Wednesday, 16 February 2000 00:57
> To: [EMAIL PROTECTED]
> Subject: EJB: Multi-threading: how to cope with the 1.1 spec?
>
>
> Hey all,
>
> So multithreading isn't really allowed in EJBs according to
> the 1.1 spec? How
> are people
> dealing with this in a netcentric architecture? I could
> see that if you have
> client control
> (thin client), that you could place the multithreading in
> the client tier.
> Since you don't
> in a browser-based environment, are most people controlling
> the multithreading
> from an access bean perspective? From .jsp?
>
> I'm curious as to what people are generally doing as a
> "best practice".
>
> Thanks,
>
> Matt Machczynski
> [EMAIL PROTECTED]
>
> ============================================================
> ===============
> 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".
>
>
===========================================================================
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".
