Re: Need help about code mobility

Gregg Wonderly <[email protected]>
Newsgroups gmane.comp.java.sun.javaspaces
Message-ID <[email protected]>
Andrea Angeloni wrote:
> ??>> Do you think this mistaken understanding of RMI codebase is common?
> ??>> Asked another way, do you think a lot of programmers view codebase
> ??>> like this?
>
> GW> I'm insterested in this as well.  That basic conceptional
> GW> misunderstanding significantly hides the details of mobile code.
>
> GW> Technically, the codebase IS a classpath extension.  But, it's a
> GW> classpath extension from the JVM receiving the remote object and
> GW> associated codebase annotation, not for the JVM exporting the remote
> GW> object.
>
> I can offer my experience: I've faced the study of these topics using some
> articles, tutorials, etc. My initial idea was to study JavaSpaces without
> having a very deep knowledge of the underground mechanisms, recovering only
> the topics encountered during the study.
> In the papers I've used, I never encountered a note like the above, or
> maybe
> I've missed it.

Well, maybe the same words have not been used before.  Some of the
simplification attempts that the J2EE world and other containers make can
actually hide a great deal of the specifics which would provide the transfer of
knowledge that would make it easy for you to grasp the specifics.

We probably should put together some better descriptions of the current state of
the art in the use of mobile code with Java and Jini.

Gregg Wonderly

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.