Hey
Imre Kifor wrote:
> The stubs that the RMI system hands out are Serializable and, by default,
> implement the client side of a simple RPC. The easiest way to create the
> stubs is to use rmic. That doesn't mean that you always have to use rmic or
> that you are restricted to using the default implementation. You can easily
> create more sophisticated stubs that implement your desired
> fault-management, load balancing, lazy-caching etc. while still taking
> advantage of the underlying services that allow you to hide (and
> transparently download) your own proxies. And do the entire thing in a
> compatible fashion.
Point taken.
> I don't see your point. If you are referring to the RMI system not defining
> a standard transaction context and/or client identity passing mechanism, I
> agree.
That is what I was referring to.
/Rickard
--
Rickard �berg
Computer Science student@LiTH
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
