Re: Generating JXTA_HOME directories for multiple peers for testing purposes

That's why I added the line under the one you quoted:

   basically passing of config data as objects vs a file ref and cache 
management
   refactoring

You are correct. Part of the issue is one of configuration and the later 
is one
of cache management. I do not have a pointer to the later on hand but 
some work
in this area has been done in the past.

I've been using #1488 and #1514 (via the JXTA Commons work) and the two 
patches
close alot of config loops as I see it.

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 



Iwan Birrer wrote:

>some remarks on the in-memory configuration:
>
>James Todd wrote:
>  
>
>> work is underway to run j2se platform in memory only
>>    
>>
>Do you refer to issue #1488 here? AFAIK, this issue addresses
>configuration only, i.e. that a peer can be configured without having to
>write a PlatformConfig file (in-memory configuration). However, it
>doesn't address other data that is stored by JXTA, e.g. the cache
>(stored in the cm directory).
>If you refer to another issue can you give me a pointer?
>
>By the way, I am using the patch of issue #1488 successfully to easily
>create different configurations for different peers (on the same host).
>
>  
>
>>   basically passing of config data as objects vs a file ref and cache
>>management
>>   refactoring
>>
>>    
>>
>
>Iwan
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
>  
>