Yeah, that's a good idea. It would be good to clarify the jSieve framework behavior. I assumed that a new instance of my test gets created every time that a script is evaluated, but maybe that's not the case.
----- "Robert Burrell Donkin" <[email protected]> wrote: > jsieve supports a number of pluggable aspects (commands, tests, > comparators) which are loaded by class name. i think that it'd be > worthwhile clarifying the contract for these pluggable components. in > particular, whether each class will be shared amongst several threads > of execution and so should be thread safe. most are - and i think it > would be best if all were - but the contract isn't clearly described > anywhere. > > opinions? > > - robert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
