[Proxool-developer] (no subject)

[Andrew B. <ne...@my...>]

Hello Bill!

Finally I have solid keyborad to type ;) I hate laptop's one ;)

> Please don't be confused with event term. Destroy method is actually
> the event the servlet receives on container state change.

>>I see. So you mean a servlet that would implement the >>destroy method an=
d
>>perhaps help to make configuration easier? I like >>that. We already (in
>>0.7) have a MonitorServlet; why not have another >>servlet for other
>>tasks. Like:

>>1. Shutting down Proxool

>>2. Configuring Proxool from file

I didn't mean any certain form of framework. The servlet container is one o=
f possible. Let it be. Again, in my case I have framework of absolutely d=
ifferent kind. In case of the servlet engine I would sugest a Proxool Con=
trol Panel having a form of servlet and swing application or a java bean =
with UI customizer. This one should connect proxool or to be forked as a =
thread. It shows real-time statistics, may configure a statistics log for=
mat. In case of Avalon framework this component could be different but st=
ill play the same role. But that's all about proxool tuning. What I meant=
 exactly is how Proxool react to framework state changes. There are few w=
ays to use proxool in servlet container. It may be a singleton serving al=
l servlets and it may be a part of one web application serving the needs =
of this web application. This is the design issue. It is not possible to =
say for sure which way is preferable. I would say that both are. It depen=
ds upon   technical requirements. So that I assume proxool is a component=
 allowing to be nested within a custom framework. To pass on framework ev=
ents the framework should provide a proxy in between, talking directly to=
 proxool. If the framework doesn't suppose proxool customization it uses =
it transparently like we have already discussed.  

Regards,
Andrew.