Hey
Sriram Srinivasan wrote:
> 2. Explicit context propagation.
More like implicit context propagation. Explicit is simple (just add
extra parameters to methods), but it would be nice if RMI/JRMP supported
implicit context propagation (which, it seems, it does. Still working on
a test-case. RMI-team(i.e. Adrian Colley) has confirmed that it should
work).
> If I didn't understand these right, ignore the rest of the message!
I didn't touch on client-side caching, which is a mess as you point out.
It will probably be interesting for some read-mostly apps, but not for
generic stuff.
> You also touched on explicit context propagation .. passing the
> context as an additional parameter.
Only internally. The app. developer should only be exposed to the "real"
interface.
My main concern was that I couldn't see any way of implementing implicit
call data and that it was hard to make the stub "clever". I have since
done some serious digging into the internal RMI-API and there seem to be
alot of goodies in there that fixes this...
/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".
