In my opinion, it really depends on the project and the environment. In my
environment with a lot of developers (32), it makes more sense to build an n-tier
framework to make a clear separation of responsibilities for the different groups. If
you are doing an application by yourself or with one or two more people, you may save
yourself some trouble going from applet to EJB.
If you are trying to build a robust B2B or banking application, you may need to go
through a servlet so that the servlet can handle any necessary socket factories to get
through the firewall; whereas, if you are building an internal bulletin board system,
the servlet may just serve as an abstraction layer.
If you are using WebSphere 3.x, you will probably need to go through the servlet
because the EJBs are going to talk RMI-IIOP - unless applets can talk RMI-IIOP - I
don't know. Most other containers, you would be safe with the RMI-JRMP.
Hope that is helpful information.
- jeremiah
------Original Message------
From: Albert Chow <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: July 27, 2000 2:12:13 PM GMT
Subject: Which architecture is better?
Hi,
I'm chosing from following two architectures :-
1. applet -> EJB -> DB
2. applet -> servlet -> EJB -> DB
Can anyone tell me which one is better?? Thanx in advance.
Albert
===========================================================================
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".
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
===========================================================================
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".
