Hi
Just a thought on the two proposed properties:
> Anyway it will be based on two properties:
>
> turbine.external.init.classname=<CLASSNAME>
> turbine.external.init.onstartup=<BOOLEAN>
>
Why not add 2 methods to the interface (one called at init() and the other
at doGet() ) and therefore eliminate the need for
turbine.external.init.onstartup=<BOOLEAN>.
Classes the just ignore the unnecessary one. A hypothetical future class
will the be able to do initialization in both cases - init() AND doGet().
On the other hand, maybe classes that don't implement the doGet()
initializer causes extra overhead for calling an empty method on every
request :-)
As I said - just some food for thought.
Leon.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
