reply-to field and replies

[Borislav Iordanov]

Cipri,

Another question to validate my understanding: seems like the
JxtaServer class doesn't provide the identity of the peer that send
the message. I imagined some JXTA-specific peerId of some sorts and I
imagined that we have map of those or something like this. But it
looks like the "reply-to" field in our own message format is what
provides the identity and that reply-to is actually a JXTA
PipeAdvertisement instance? How is it serialized - as XML I suppose?

Anyway, I'm surprised that we need to track the sender of a message
ourselves with JXTA....or we don't?

Boris
--
"Frozen brains tell no tales."

-- Buckethead

[Ciprian Costa]

Hi Boris
  
   We have a map of known peers that is maintained by listening to advertisements in the network (in the DefaultJXTANetwork class). I am sure that we can get JXTAServer to reveal detailed information about the sender, but I wanted to somehow separate the identity of a "logical" sender. The message could (eventually) come from many sources so I did not want to tie it to the JXTA infrastructure. We could enhance the mechanism and have JXTAServer inject the reply-to field in the message, so that we do not send it over the network, but I think the message should contain all the identification of the sender adn destination. Another thing here is that the reply-to field could not be the same as a sender (a peer could just be sending a message and request for the reply to be sent to another peer).

regards,
Cipri