Hello Andrew,
just a ranting coming, sorry. :-)
What do you need the GUID for?
Of course you need it. I just put this rhetorical question, because i see
Shoal as a pre-setup way to get peers grouped together and you can send messages
to one, all or just a couple of peers. Plus some utilities on top of it.
No need to know PeerID or GroupID. In fact, JXTA "is not required."
-> So what do you have: a map with known peers. And methods for receiving/sending bytes
to peers. Plus some utilities and hooks to hang yourself in to get notifications.
-> Everything else like key exchange you would build on top of that.
If you need the concepts of PeerID and GroupID and announcements, you are back to JXTA.
At the moment i use shoal just for peer detection. I dont send messages, i dont receive
messages. And to me its very problematic. It takes sometimes alot before a peer is seen
by others as well it takes time, before they are not seen anymore. Sometimes it happens,
that a peer is anyhow in a not usable state. We had cases, where peers had data of 0.5GB
in memory in any queues, maps, lists, as if the data cant be delivered.
I am back to JXTA, switching off multicast, using rendezvous peers, my own announcements,
etc..
On Wed, Dec 17, 2008 at 11:12:45AM +1100, Roo wrote:
> Am I right in thinking it appears the shoal implementation is deliberately (or m
> aybe unknowingly) making it difficult to get the GUID for a peer?