Re: Re: [JXTA dev] Private vs Secure groups etc.

Hey Todd,

    thanks much for the info - yes, if you could send me refs to 
String/text based auth that would
suffice. I will work on building with that and send feedback to the list 
of anything I discover that
is worth mentioning.

Cheers

James Todd wrote:

>
> MyJXTA currently supports groups w/ null membership (aka anonyous) and 
> string/text based
> authentication. We do not yet support PSE (credentialed) group 
> membership but are looking
> to do so soon.
>
> If you are interested in string/text based authentication I can help 
> provide references to
> the relevant code fragements.
>
> The JXTA wiki includes notes on PeerGroup membership and a PSE Group 
> Membership code sample
> is included in the Platfrom repostiory ... the later of which we will 
> use as a template to
> add PSE group membership.
>
> Re MyJXTA and secure groups, we will likely support group create of 
> anonymous and PSE groups
> yet support group join of anonymous, string and PSE groups. In other 
> words, we wish to no
> longer create string based membership but will support joining such 
> groups there were potentially
> created out-of-band, eg Shell.
>
> hth,
>
> - james
>
> -- 
> James Todd :: blogs.sun.com/gonzo | weblogs.java.net/blog/gonzo
>
> MyJXTA :: use it - learn it - do it
>
> Java == platform independence
> XML  == application independence
> JXTA == network independence
>
> Secure End-to-End Computing
>
>
> Demetris G wrote:
>
>>
>> How succesfull is everyone in building secure groups ? Anyone who has 
>> been playing with that
>> can you please throw some light on the process that is needed to be 
>> followed to accomplish this -
>> I used the procedures listed on Twiki, the peers find the group, the 
>> authentication credentials
>> seem to be loaded correctly, however the authentication hangs. Would 
>> code in MyJXTA
>> help out with this - if yes just say the word and I will find it.
>>
>> And which documentation is this refering to ?
>>    * Consult the documentation for the specific Membership Service
>>    * you are using for details on how this information is used (if at 
>> all).
>>    **/
>>    public AuthenticationCredential( PeerGroup peergroup, String 
>> method, Element indentityInfo )
>>
>> Thanks much
>>
>> James Todd wrote:
>>
>>>
>>> Yes. For MyJXTA we choose a value of 2 minutes. A best practice 
>>> appears to be
>>> to use that value consistently for all edge applications which join 
>>> subgroups,
>>> aka application groups.
>>>
>>> hth,
>>>
>>> - james
>>>
>>> -- 
>>> James Todd :: blogs.sun.com/gonzo | weblogs.java.net/blog/gonzo
>>> MyJXTA :: use it - learn it - do it
>>>
>>> Java == platform independence
>>> XML  == application independence
>>> JXTA == network independence
>>>
>>> Secure End-to-End Computing
>>>
>>> Poole, Paul P1 wrote:
>>>
>>>> So, by default, autostart is enabled in MyJXTA?
>>>>
>>>> -----Original Message-----
>>>> From: [email protected] [mailto:[email protected]] Sent: Tuesday, 
>>>> July 26, 2005 11:15 AM
>>>> To: [email protected]
>>>> Subject: Re: [JXTA user] Became Rendezvous Peer
>>>>
>>>>
>>>>
>>>> The "auto start" method, last of the 3 in my response, is specifically
>>>> designed for this scenario in mind.
>>>>
>>>> MyJXTA does this for each subgroup, not NetPeerGroup, that it joins.
>>>> Selecting a relevant timing threshold (the period) is key for
>>>> application deployments such that they don't all rush to become 
>>>> rdvs too
>>>> quickly yet they don't linger too long either, seeking an available 
>>>> Rdv
>>>> with which to obtain a lease from.
>>>>
>>>> MyJXTA does this in:
>>>>
>>>>   /net/jxta/myjxta/MyJXTA.joinGroup(Group, boolean, boolean, boolean,
>>>> int)
>>>>
>>>>   last line of that method
>>>>
>>>> hth,
>>>>
>>>> - james
>>>>
>>>> -- 
>>>> James Todd :: blogs.sun.com/gonzo | weblogs.java.net/blog/gonzo
>>>> MyJXTA :: use it - learn it - do it
>>>>
>>>> Java == platform independence
>>>> XML  == application independence
>>>> JXTA == network independence
>>>>
>>>> Secure End-to-End Computing
>>>>
>>>> Poole, Paul P1 wrote:
>>>>
>>>>> Along this line of questioning...
>>>>>
>>>>> If a peer is unable to find a rendezvous peer, what configuration 
>>>>> is required (if any) to ensure that the peer will automatically 
>>>>> become a rendezvous peer?
>>>>>
>>>>> Thanks...
>>>>>
>>>>> -Paul
>>>>>
>>>>> -----Original Message-----
>>>>> From: [email protected] [mailto:[email protected]]
>>>>> Sent: Tuesday, July 26, 2005 11:04 AM
>>>>> To: [email protected]
>>>>> Subject: Re: [JXTA user] Became Rendezvous Peer
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> How does a peer become a rendezvous peer?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 3 ways:
>>>>>
>>>>>  as configured for the app NetPeerGroup
>>>>>
>>>>>  via the RendezVousService
>>>>>
>>>>>    PeerGroup.getRendezVousService().startRendezVous()
>>>>>    PeerGroup.getRendezVousService().stopRendezVous()
>>>>>
>>>>>  via "autostart"
>>>>>
>>>>>    PeerGroup.getRendezVousService().setAutoStart(boolean enabled, 
>>>>> long
>>>>> period)
>>>>>
>>>>> For prototypical edge applications, the autostart method is likely 
>>>>> your best bet.
>>>>>
>>>>> hth,
>>>>>
>>>>> - james
>>>>>
>>>>> -- 
>>>>> James Todd :: blogs.sun.com/gonzo | weblogs.java.net/blog/gonzo
>>>>>
>>>>> MyJXTA :: use it - learn it - do it
>>>>>
>>>>> Java == platform independence
>>>>> XML  == application independence
>>>>> JXTA == network independence
>>>>>
>>>>> Secure End-to-End Computing
>>>>>
>>>>>
>>>>> Fabrizio Marozzo wrote:
>>>>>
>>>>>
>>>>>> How does a peer become a rendezvous peer?
>>>>>> The peer must implements any interface.........?
>>>>>> Please
>>>>>> Fabrizio
>>>>>>
>>>>>> --------------------------------------------------------------------- 
>>>>>>
>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>> For additional commands, e-mail: [email protected]
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>