I agree. But that was one of the benefits stated for asynchronous EJB
servers -- to allow the user (or UI) to continue working while a server
request is being process (in other words, the client can multi-thread their
work).
-Ron
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Sam Shirah
> Sent: Wednesday, October 20, 1999 1:30 PM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB cons?
>
>
> Hi Ron,
>
> Without putting words into anyone else's mouth, asynchronous
> processing
> does not necessarily imply multithreading.
>
>
> Joe Sam
>
>
> Joe Sam Shirah
> Autumn Software
> What you don't know DOES hurt you...and your business
> ___________________________________________
>
> -----Original Message-----
> From: Ron Yust <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Wednesday, October 20, 1999 12:46 PM
> Subject: Re: EJB cons?
>
>
> >"However, the largest transaction processing systems in the world are
> >virtually all asynchronous."
> >
> >You are talking about CICS aren't you? All those CICS/COBOL programs are
> >single-tasking.
> >CICS-call...wait...CICS-call...wait...CICS-call...wait........
> >
> >The bulk of high volume transaction systems are still on mainframes and
> >their end-users are still not multi-threading regardless whether the UI
> can.
>
> ==================================================================
> =========
> 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".
