Re: [carol] Carol configuration for handling all features request

[Florent BENOIT <Florent.BENOIT@xxxxxxxxxxxxx>]

Bordet, Simone wrote:

> The solution Florent sketched, a class that acts as a configuration 
> repository with static methods, and a configuration class that loads 
> configurations should work well.
> If the repository class is also a factory for configurations, and the 
> configuration class is an interface with a default implementation, I think 
> it's best.
>
>  
If repository is a factory, it will return empty configuration ? 
configuration with values of carol-default.properties ?
Do we have to send arguments to the factory class for retrieve a 
configuration object ?
Do you have ideas on the factory methods that you want ?

The interface + default implementation seems to be a good choice. It is 
up to us to take a good interface :)

> and a configuration class that loads configurations

So it means that a class will take carol.properties file and call 
factory for create each configuration present in this file.
(a replacement URL could be given instead of taking carol.properties 
file with classpath, we can reload a new configuration later...)

> > This can also allow (I think) to change on the client side 
> > the context used.
> > One JVM could have two clients, one using jrmp, other using iiop. (by 
> > changing the current carol config on the calling thread).
> >    
>
> Will this be handled by carol code, or the user code must explicitely 
> change the configuration for the calling thread ?
>
>  
Carol should handle only a default config when running in multi-config 
mode on client case. (on server, it will call each configuration)
I think that this is to the developer to explicitely set the config. 
Maybe that it is possible without explicitely calls but I don't see how 
for now.

Regards,

Florent

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature