> "Poska, Neil" wrote:
> >
> > In a previous discussion about applet to session bean communication, Tom
> > Valesky made the following statement:
> >
> > <quote>
> > >3) You're probably better off using servlets to encapsulate your EJB
> > >logic
> > >and passing only HTML/HTTP over the internet.
> > <unquote>
> >
> > Why is this? Are there technical, performance or security reasons why
> > this is so? Is this a 'bad idea', or just 'not recommended' for some reason?
A couple of reasons:
1) Some of the RMI support classes required in some EJB implementation are
quite large, requiring the user to download on order of 1 MB of .jar
files.
2) You'll have a lot less support headaches with HTTP than you will trying
to get JRMP or IIOP working end-to-end from the random client, through
their network, through the internet, and through your network.
Tom
============================================================================
Tom Valesky -- [EMAIL PROTECTED] -- http://www.patriot.net/users/tvalesky
===========================================================================
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".
