I'm still banging my head on the Great Wall (aka Jonathan). Having set out
to produce a program being able to use the TcpIpProtocol.java as a base for
my communication of the classic first words ("Hello world!"), I do have to
admit meeting more trolls then I appreciate.
I therefore post some rather broad questions regarding the functionality of
certain mechanisms in the core of the Jonathan personality.
1. How does the bind-method in the implementations of SessionIdentifier
really work? What is it supposed to do, and how do we go about using it in
both client and server cases?
2. What is the inner workings and motivation for using both
SessionIdentifiers and Session_Low objects when binding to obtain a
Session_High? It seems to me that having to connect to a remote machine to
obtain a SessionIdentifier, and thereafter provide a Session_Low (which is
situated on the remote machine, if I'm not mistaken) seems a little
backward. Do I have to provide the actual object with which I want to
communicate, or does it suffice to send an object of the same type. If the
former is the case, how on earth am I supposed to send the object in
Jonathan without resorting to some dirty RMI-tricks?
As I've got quite a lot of non-working code trying to communicate with
itself, I wonder if it is considered bad form to post links to code on this
list? If not, I'll post a link to my (almost properly javadoced) "'ello
worldie" in the near future. (In the vain hope that somebody will actually
take a look at it, of course :o)
Thank you for your time and patience
Per Christian Nodtvedt
--
"Denne meldingen er p� portugisisk n�r dere ikke leser den."
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonathan".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
