Menu
▾
▴
|
From: Andrew B. <ne...@my...> - 2003-02-05 10:02:05
|
Hi All! > Of course the customization requires from user to use pool facade > directly.=20 Not true. At least, if I understand you correctly. You can configure Proxool using a Properties object sent to the Driver. It is the clumsiest way of configuring it but it is there for precisely that reason. [The JAXPConfjigurator is the nicest way :)] -------------------8<-------------------------------- I had to say that I was not going to hightlight the only problems. I descri= bed how the design in my opninion should look like. I didn't mean that th= is feature is absent. I am aware of properties based way of pool configur= ation. I just selected of few leveles of responsibility. Please don't get= it serious. If you remebered I divided the pool behaviour on two parts: = default (transparent) and customized. The customization as a term require= s user participation in general. -------------------8<-------------------------------- > I would recom=D1=8Cend to make a wrapper around pool facade reinitializin= g > the pool on getting servlet events. But then what API does the wrapper adhere to? Is there a spec. for servlets doing this? --------------8<--------------------- Please don't be confused with event term. Destroy method is actually the ev= ent the servlet receives on container state change. --------------8<--------------------- > I am sorry for such a long essay I welcome it. Keep it up, Andrew. Out of our differences and misunderstandings will rise a better Proxool :) --------------8<--------------------- No doubts! :) --------------8<--------------------- Andrew. |
|
From: Andrew B. <ne...@my...> - 2003-02-05 10:02:06
|
Hi All! > Of course the customization requires from user to use pool facade > directly.=20 Not true. At least, if I understand you correctly. You can configure Proxool using a Properties object sent to the Driver. It is the clumsiest way of configuring it but it is there for precisely that reason. [The JAXPConfjigurator is the nicest way :)] -------------------8<-------------------------------- I had to say that I was not going to hightlight the only problems. I descri= bed how the design in my opninion should look like. I didn't mean that th= is feature is absent. I am aware of properties based way of pool configur= ation. I just selected of few leveles of responsibility. Please don't get= it serious. If you remebered I divided the pool behaviour on two parts: = default (transparent) and customized. The customization as a term require= s user participation in general. -------------------8<-------------------------------- > I would recom=D1=8Cend to make a wrapper around pool facade reinitializin= g > the pool on getting servlet events. But then what API does the wrapper adhere to? Is there a spec. for servlets doing this? --------------8<--------------------- Please don't be confused with event term. Destroy method is actually the ev= ent the servlet receives on container state change. --------------8<--------------------- > I am sorry for such a long essay I welcome it. Keep it up, Andrew. Out of our differences and misunderstandings will rise a better Proxool :) --------------8<--------------------- No doubts! :) --------------8<--------------------- Andrew. |
|
From: Andrew B. <ne...@my...> - 2003-02-05 10:02:06
|
Hi All! > Of course the customization requires from user to use pool facade > directly.=20 Not true. At least, if I understand you correctly. You can configure Proxool using a Properties object sent to the Driver. It is the clumsiest way of configuring it but it is there for precisely that reason. [The JAXPConfjigurator is the nicest way :)] -------------------8<-------------------------------- I had to say that I was not going to hightlight the only problems. I descri= bed how the design in my opninion should look like. I didn't mean that th= is feature is absent. I am aware of properties based way of pool configur= ation. I just selected of few leveles of responsibility. Please don't get= it serious. If you remebered I divided the pool behaviour on two parts: = default (transparent) and customized. The customization as a term require= s user participation in general. -------------------8<-------------------------------- > I would recom=D1=8Cend to make a wrapper around pool facade reinitializin= g > the pool on getting servlet events. But then what API does the wrapper adhere to? Is there a spec. for servlets doing this? --------------8<--------------------- Please don't be confused with event term. Destroy method is actually the ev= ent the servlet receives on container state change. --------------8<--------------------- > I am sorry for such a long essay I welcome it. Keep it up, Andrew. Out of our differences and misunderstandings will rise a better Proxool :) --------------8<--------------------- No doubts! :) --------------8<--------------------- Andrew. |
|
From: Bill H. <bi...@lo...> - 2003-02-05 11:21:24
|
Hi Andrew, On Wed, 2003-02-05 at 09:36, Andrew Budarevsky wrote: > 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 and 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 -- Bill Horsman Proxool http://proxool.sourceforge.net ICQ: 119577180 |
