|
Replies:
0
|
|
|
|
|
|
|
Migration 2.4.1 to 2.5.0 question
Posted:
Aug 19, 2008 2:31 AM
|
|
|
Hi,
I am currently trying to upgrade my JXTA code from 2.4.1 to 2.5.0, and aim to make it 'state of the art'. However, I am facing a 'best practices' problem which I am not quite sure how to resolve.
In the older versions of JXTA, the idea was that you discovered/created a peer group in which you published a module class advertisement and module spec advertisement which provided information about the actual connection. In my code, I used this to make a JxtaSocket. My code was based on "JXTA in a Nutshell" and an older book "JXTA: Java P2P Programming", both based on JXTA 2.4.x
In 2.5.0 (especially reading the programming guide) I get the feeling that discovering/creating peergroups is no longer a best practice. Instead, you discover/create modele spec advertisements immediately and work with these. Reading some forums, I got the idea that peergroups are created automagically 'under the hood' and do not need to be specifically discovered or created.
I could go along with this, but then I don't see how I can start a JXTA socket, because this requires a peergroup in its constructor. The examples with JxtaSocket use the netpeergroup, but I would think that the best practice would be to attach the jxtasocket to a module spec advertisement.
So my question is, what the recommended way would be to use JXTA sockets using 2.5.0.
Kees
|
|
|
|
java.net RSS
