On 3/23/06, Peter Bex <[EMAIL PROTECTED]> wrote: > > > > Using parameters for all configuration options wasn't such a great idea > > from the beginning. It makes sense to use parameters, when you want > > thread-local options, but the spiffy configuration should be applied > > to all threads anyway. Note that thread-specific parameters are still > > that: parameters. > > I have to disagree. They /were/ a very good idea, since they allow you > to fire up multiple instances of spiffy with different configurations > (like on several ports) from one application.
In that case a configuration object packaging all options would have been the optimal solution. But I think running multiple spiffy instances in the same process isn't such a great idea anyway, opposed to running them in separate processes. cheers, felix _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
