Kinda like the old saying "if you don't like America, leave it". No, I want
to change it. EJB has great promise, but it's going in directions I think
is wrong.
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tye, Tim
> Sent: Tuesday, October 26, 1999 4:24 PM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB Restrictions-- threads, io
>
>
> Do it. RMI is the correct answer for many applications. It has
> less overhead, and allows the designer to do anything.
> However, RMI does not provide security, transaction control,
> caching, or isolation like the EJB container.
>
> Always use the tool that meets the requirements of the job.
>
> Don't use EJB just because your management says it is hot.
>
>
> -----Original Message-----
> From: Ron Yust [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 26, 1999 2:57 PM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB Restrictions-- threads, io
>
>
> Paul,
>
> Wow! No static methods/data, no file i/o, no threads, no
> sockets, no native
> code. Sounds like EJB is an unruly teenager about to take the family car
> out on a date. Geeesh, just neuter the EJB application! I may end up
> sticking with my trusty old RMI server.
>
> -Ron
>
> ==================================================================
> =========
> 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".
