Re: EJB cons?

[Ron Yust]

Title: 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.

-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Erik Huddleston
Sent: Wednesday, October 20, 1999 9:53 AM
To: [EMAIL PROTECTED]
Subject: Re: EJB cons?

When you use the terms "clients" and "user" what are you referring to?  If you mean the end user, then most UI's hide this from the end user.  If you mean the calling application, then yes, you are correct.  Asynchronous programming is _much_ harder than the synchronous model we are accustomed to.  However, the largest transaction processing systems in the world are virtually all asynchronous.

 

I am looking forward to having asynchronous components in the EJB model.  If anyone has url's to Sun's proposals on the subject, I would appreciate hearing about them.

 

 

Erik

--
Erik Huddleston, [EMAIL PROTECTED]
Chief Architect, eCustomers.com
Microsoft Java MVP

-----Original Message-----
From: Ron Yust [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 20, 1999 9:50 AM
To: [EMAIL PROTECTED]
Subject: Re: EJB cons?

It's been my experience in large transaction systems that the majority of clients need to wait for a transaction to complete (synchronous) before doing anything else.  The user is expecting to complete a business process and will wait before continuing with other work.  Users are not as adept as multithreading as computers.

 

I think the synchronous model for EJB is intended for the bulk of business-oriented transactions initiated by end-users.  Using EJB for asynchronous transactions is ideal but better suited for electronic-initiated transactions between computer systems.

-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Erik Huddleston
Sent: Wednesday, October 20, 1999 8:46 AM
To: [EMAIL PROTECTED]
Subject: Re: EJB cons?

If I make a call, I must wait for a response.  Many TP systems use an asynchronous paradigm for increased scalability.  I would suggest reading Principles of Transaction Processing by Philip Bernstein and Brian Newcomber for thorough introductory coverage of the area.

Erik
--
Erik Huddleston, [EMAIL PROTECTED]
Chief Architect, eCustomers.com
Microsoft Java MVP

> -----Original Message-----
> From: Pankaj Tandon [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 20, 1999 7:45 AM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB cons?
>
>
> Can you please elaborate on what you mean by eJB being a
> synchronous model.
> (An example would really help).
> Thanks
>
>
>
>
>
> Ian McCallion <[EMAIL PROTECTED]> on 10/20/99 08:04:45 AM
>
> Please respond to A mailing list for Enterprise JavaBeans development
>       <[EMAIL PROTECTED]>
>
> To:   [EMAIL PROTECTED]
> cc:    (bcc: pankaj tandon/MIS/genco/US)
> Subject:  Re: EJB cons?
>
>
>
>
> Youval Bronicki wrote:
>
> > We are considering to use EJB for an n-tier product. 
> Almost everything
> > we've read seems to support EJB.
>
> > Can somebody list any issues that may discourage us (or point to a
> relevant
> > resource)?
>
> EJB's main weakness today is that is is a synchronous model.
> You'll need to
> wait
> for EJB2 (or go with proprietary extensions, which a couple of vendors
> have) if
> you want integration with asynchronous messaging.
>
> > Is CORBA + CORBA Services a serious competitor?
>
> No. The only serious competitor is the highly proprietary
> COM/DCOM from
> you-know-who.
>
> 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".
>
> ==============================================================
> =============
> 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".
>