You should go for Servlet and EJB since the EJB spec offers so many great
features for building enterprise applications such pooling,
synchronization.... and also the protocol RMI/IIOP is much much robust than
the RMI protocol itself. Anyway, the industry now only talks about EJB.
>From: Shaila C D <[EMAIL PROTECTED]>
>Reply-To: "A mailing list for discussion about Sun Microsystem's Java
> Servlet API Technology." <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Servlet-RMI-EJB
>Date: Fri, 2 Jun 2000 15:18:22 +0530
>
>Hi,
>
> Can anybody suggest - how do we make a choice between Servlet, EJB and
>RMI
>for a particular application, when all the three can be used as middle tier
>
>Thanks.
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
