Re: Generating JXTA_HOME directories for multiple peers for testing purposes

There is no issue or current plan to provide an in-memory cache manager, 
however the JXME CDC binding already provides such a feature which is 
based on an LRUCache (which was recently introduced in the platform for 
to address a ProxyService bug). It would not be too much work to forward 
port such feature into the platform where the  bulk of the  work would 
around cm configuration and selection (persistent vs. in-memory).

Also keep in mind that relying on an in-memory cache means that 
configuration must either be persisted by the application, or 
programatically generated where some careful thought must be given to 
how to best generate a PeerID (dynamic, or repeatable through encoding 
of device id, mac, etc.).


Mohamed


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]
>
>