Re: [JXTA dev] ext:config addition

OK.

I greatly appreciated talking this through. Truly.

Now, the "bootstrap" field/scaler is going to migrate to host w/in the /jxta/network/rendezVous
and /jxta/network/relays elements shortly as PlatformConfig can, in turn, host lists of bootstrap
addresses.

Taking that into consideration, we could add an "enabled" attribute to each nested address
element, the default of which is true.

I still need to think this one through ... and folks thoughts on the topic are appreciated
... but I have a suspicion that the proposed boolean attribute isn't enough. For example,
we will run into ext:config and PlatformConfig discontinuities and the like.

We'll get there.

- 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 


Vanessa Williams wrote:
> 
> On 26-Jul-05, at 10:58 AM, James Todd wrote:
> 
>>
>> What if we added an "enabled" attribute to /jxta/network/ 
>> [rendezVous,relays]@enabled?
>>
>> The default might be "true" so as to represent the common use case  of 
>> Profile.EDGE
>> but one could specify false for isolated super and/or local profiles.
>>
>> This is sounding like the right fix to me, having thought this  
>> through a bit on
>> the lists (thx Vanessa) et al.
>>
>> What say you?
>>
>> hth,
>>
>> - james
> 
> 
> Sounds reasonable to me. I assume that enabled="false" implies that  
> there is to be no bootstrap address, as well as no seeds?
> 
> We still need a way to have enabled="true" and no bootstrap address.  
> Otherwise, the default bootstrap address is automagically used and  
> that's not good if you're trying to keep your network isolated, IMHO.
> 
> Cheers,
> 
> V.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>