Menu
▾
▴
proxool-developer
|
From: <mar...@sy...> - 2003-02-24 12:19:41
|
Haven't had a chance to try the AdminServlet so maybe this is already there and is more duplication. Would an XML-RPC or SOAP interface be useful for remote management of pools? I guess just implementing the ProxoolFacade class? Might be a useful option to handle to support the switching of database URLs in failover situations on non-servlet solutions (i.e. bundle with the driver, and activate via XML or Properties). Other thoughts is looking at other "delfacto" frameworks like Struts, Maverin, etc, and see what simple hooks we can provide to make integration seemless. Also I've been using Hibernate (http://hibernate.sf.net) lately, and have contributed a little documentation and feedback on version 2.0 which is still in beta. Would be nice to provide a Proxool integration as one of the pool managers it would use. I'll look into maybe working on this. Now I'm just dreaming... (A voice from the front of the class) Hey, dreamer boy get back to your documentation! Martin PS: On the URL question: Close all the connections immediately on a URL change is my vote. I think the fail-over features will be a really unique selling feature for Proxool. Worth some effort on the niceties. > > From: Bill Horsman <bi...@lo...> > Date: 2003/02/24 Mon AM 06:17:50 EST > To: Proxool Developer List <pro...@li...> > Subject: [Proxool-developer] Getting ready for 1.0 > > Hi all, > > What do we need to do to reach 1.0? I think we're _almost_ there. Martin > and Christian are working on DocBook and Christian is completing a JMX > implementation for 0.8. > > I'd like to make the new AdminServlet a bit better: make it possible to > update the definition for each pool. Perhaps provide some more > descriptive information about what all the definitions mean. > > Does anyone want to lobby for any other simple features that we could > include. I don't want to do anything fundamental that will delay 1.0 - > things like failover database switching can wait until 1.1. > > Cheers, > -- > Bill Horsman > Proxool > http://proxool.sourceforge.net > ICQ: 119577180 > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Proxool-developer mailing list > Pro...@li... > https://lists.sourceforge.net/lists/listinfo/proxool-developer > |
|
From: Christian N. <chr...@em...> - 2003-02-24 14:11:54
|
> Would an XML-RPC or SOAP > interface be useful for remote management > of pools? I guess just implementing the > ProxoolFacade class? +1 CHR -- _______________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup |
|
From: Bill H. <bi...@lo...> - 2003-02-24 17:59:58
|
On Mon, 2003-02-24 at 16:31, Martin Crawford wrote: > The apache libraries best to consider are: > http://ws.apache.org/xmlrpc/ > http://ws.apache.org/soap/index.html <snip> > Actually what I meant was implementing an XML-RPC and/or SOAP layer to > support the ProxoolFacade. Sounds good. > Now this would be cool. Acutally I again was referring that the XML-RPC > and/or SOAP layers would be useful to manually redirect/switch over, but > automatic is much cooler! Yeah, that's what we thought. I think it might take a while to get it to behave properly and mature a little though. So planned for 1.1 (but those no reason why 1.1 shouldn't happen within the next few months). > I guess the overall idea is to find > ways to make Proxool easily pluginable to any framework to make it more > marketable. Yep. > Hibernate has built in a "non-production" ready pool manager. But for > production it provides either pool manager hooks to use either c3po, > DBCP or a DataSource (BTW this would be another good thing to support, > but this is an old request I think). Yeah, we'll take a deep breath and support DataSource sometime. 1.1+ I think. > We would only need to implement > this interface http://hibernate.bluemars.net/hib_docs/api/ and come up > with a similar property passing solution as > http://hibernate.bluemars.net/hib_docs/reference/html/session-configuration.html#session-configuration-s4. Yep, looks like that would be fairly simple to implement. Presumably, we could then contribute our ProxoolConnectionProvider to the Hibernate project? Do you have some contacts from Hibernate so that we can discuss how best to do this? I don't suppose they'll want to add Proxool support until we are at 1.0. And that won't be for another month (I'm guessing). > >My opinion is that we shouldn't try and squeeze much more into 1.0 and > >we should plant our feet firmly in the ground and say "it's ready!". > > > > > I fully agree, but you ask for the shopping list;) Yeah, I asked for it! I think I'll add a RoadMap to the web site for all this stuff. But I suppose I should wait for your doc freeze to be complete first. Actually, I am just making a link fix now. Perhaps I should just tell you what it is: listen.html has links to: api/org/logicalcobwebs/proxool/StatisticsListenerIF.html, and api/org/logicalcobwebs/proxool/StatisticsIF.html they should have the admin package in the path: api/org/logicalcobwebs/proxool/admin/StatisticsListenerIF.html, and api/org/logicalcobwebs/proxool/admin/StatisticsIF.html > Although it would be good to have support for Hibernate 2.0 before it is > release (there are no dates but I imagine soon). I feel it will probably > become a high profile project with this release and it would be great > "marketing" to be associated with it.... Yeah, it would be great to be associated with Hibernate. Do you want to talk to them, or shall I? -- Bill Horsman Proxool http://proxool.sourceforge.net ICQ: 119577180 |
|
From: Martin C. <mus...@us...> - 2003-02-24 18:08:15
|
> > Yeah, we'll take a deep breath and support DataSource sometime. 1.1+ I > think. Yeah.. no rush, but certainly a must at somepoint.... And don't ask me to do it;) > > I don't suppose they'll want to add Proxool support > until we are at 1.0. And that won't be for another month (I'm guessing). > Timing would proabably be okay. Perhaps even for 1.1 if it was a soon release. There is no real indication of when Hibernate 2.0 is going to be release. But probably getting in before the next beta would be good. > >>>My opinion is that we shouldn't try and squeeze much more into 1.0 and >>>we should plant our feet firmly in the ground and say "it's ready!". >>> Yup. I agree too. > Yeah, I asked for it! I think I'll add a RoadMap to the web site for all > this stuff. But I suppose I should wait for your doc freeze to be > complete first. Actually, I am just making a link fix now. Perhaps I > should just tell you what it is: > > listen.html has links to: > api/org/logicalcobwebs/proxool/StatisticsListenerIF.html, and > api/org/logicalcobwebs/proxool/StatisticsIF.html > > they should have the admin package in the path: > api/org/logicalcobwebs/proxool/admin/StatisticsListenerIF.html, and > api/org/logicalcobwebs/proxool/admin/StatisticsIF.html > No prob. I haven't started yet:) > > Yeah, it would be great to be associated with Hibernate. Do you want to > talk to them, or shall I? I've already popped my little nose around the project contributing a doc on Hibernate and XDoclet, and made an important feature request (yes, I only ask for the world on a platter;), I'd imagine it would be easy to get them on board for the Proxool support. Now I've never used c3po or DBCP, but can someone point out what our differences incase they ask. Martin |
|
From: Bill H. <bi...@lo...> - 2003-02-24 18:18:21
|
On Mon, 2003-02-24 at 18:09, Martin Crawford wrote: > Now I've never used c3po or DBCP, but can someone point out what our > differences incase they ask. c3p0 doesn't offer much on the web site. Still in alpha, no activity, no doc. I don't want to dis the project, but it would imply that we don't have to be at 1.0 to be included in Hibernate :) dbcp on the other hand comes from the mighty Jakarta Commons and will get a lot of respect because of that. But we seem to be a little maturer and have a lot better doc. -- Bill Horsman Proxool http://proxool.sourceforge.net ICQ: 119577180 |
|
From: Martin C. <mus...@us...> - 2003-02-26 18:40:19
|
> Yeah, we'll take a deep breath and support DataSource sometime. 1.1+ I > think. Sorry another competing feature that came to my attention from the Hibernate project is a Statement Cache. Not really sure "what" that implies, but DBCP offers it;) I guess it either will cache prepared statements or perhaps even non-prepared statements accorss connections. Roadmap that to 1.1... Also on the Hibernate support I've spoken with the PM and he seems accepting and it's tiny bit of code to write to implement. After the documentation I can work on this. Trying to figure out who's code it will be, Hibernate or Proxool. Cheers. Martin |
|
From: Bill H. <bi...@lo...> - 2003-02-26 19:44:56
|
On Wed, 2003-02-26 at 18:41, Martin Crawford wrote: > Statement Cache I'm not sure whether we should... > DBCP offers it Right! We will too then :) > Roadmap that to 1.1... I'll try and fix up a Roadmap page on the web site. > Also on the Hibernate support I've spoken with the PM and he seems > accepting and it's tiny bit of code to write to implement. After the > documentation I can work on this. Trying to figure out who's code it > will be, Hibernate or Proxool. I think it will all be within Hibernate. Good work! It will be great to be included. Let me know if I can help with the adapter (or whatever it is). One thing I have just changed in anticipation of this is that it's now possible to define the url and the driver as properties rather than specifying them in the url. I have to do some testing on that though, but I'll let you know... Cheers, -- Bill Horsman Proxool http://proxool.sourceforge.net ICQ: 119577180 |
|
From: Bill H. <bi...@lo...> - 2003-02-24 14:04:09
|
On Mon, 2003-02-24 at 12:19, mar...@sy... wrote: > Would an XML-RPC or SOAP interface be useful for remote management of > pools? Sounds interesting. I don't know much about XML-RPC/SOAP though. > I guess just implementing the ProxoolFacade class? Well, ProxoolFacade isn't an interface :) It could use ProxoolFacade if it liked. > Might be a useful option to handle to support the switching of > database URLs in failover situations on non-servlet solutions (i.e. > bundle with the driver, and activate via XML or Properties). We already allow switching of databases: either programmatically, or with the upcoming JMX component or with the next version of AdminServlet. If you mean _automatic_ switching then this is something that Del Simmons has been talking about for a while. It would be really cool and will probably be in 1.1. > Other thoughts is looking at other "delfacto" frameworks like Struts, > Maverin, etc, and see what simple hooks we can provide to make > integration seemless. I know Struts quite well and I can't really think of anything we could do that isn't already provided by the AdminServlet. We could produce a Struts version of the AdminServlet (called, say, AdminAction) but it would just end up duplicating AdminServlet. (Background: AdminServlet does everything in a very simple way: HTML is coded in the Java class, request parameters are extracted manually. All the things that would make a servlet app a nightmare, and how we used to do it a long time ago. However, because the scope of the servlet isn't very much, the advantages we get in very simple configuration - no JSPs - outweigh this, I believe.) We do already provide an AvalonConfigurator. What's Maverin? > Also I've been using Hibernate (http://hibernate.sf.net) lately, and > have contributed a little documentation and feedback on version 2.0 > which is still in beta. Would be nice to provide a Proxool integration > as one of the pool managers it would use. I'll look into maybe working > on this. I'd be interested to learn how we can integrate with Hibernate. Doesn't it just rely on any JDBC driver, or is it more complicated than that? --- I think my question could actually be better rephrased as: "are there any changes/features that should be in 1.0 rather than later?" Or to attempt that again, "what are the objectives of a 1.0 release?" I would suggest the miniumum is: 1) Robustness: no critical bugs (we have no bugs at all just now) 2) Fixed API (we have already fixed the API so that code that works with 0.7 will (probably) work with 1.0. 3) Very good documentation. We're nearly there with this. Even closer with DocBook. 4) Easy configuration. I think we are there with 0.7. So, the list beyond that is just additional features that make us competitive with the other pools. Like JMX (coming in 0.8), SOAP?, and so on. My opinion is that we shouldn't try and squeeze much more into 1.0 and we should plant our feet firmly in the ground and say "it's ready!". > Hey, dreamer boy get back to your documentation! Keep up with the good work, Martin! Cheers, -- Bill Horsman Proxool http://proxool.sourceforge.net ICQ: 119577180 |
|
From: Martin C. <mus...@us...> - 2003-02-24 16:30:01
|
> > >Sounds interesting. I don't know much about XML-RPC/SOAP though. > They are two standards for remote method invocation based on XML. For example (http://www.xmlrpc.org/) for details about the one spec (this one is very lightweight IMHO than SOAP, but the industry likes SOAP because it's more featureful). The apache libraries best to consider are: http://ws.apache.org/xmlrpc/ http://ws.apache.org/soap/index.html > > >>I guess just implementing the ProxoolFacade class? >> >> > >Well, ProxoolFacade isn't an interface :) It could use ProxoolFacade if >it liked. > > Actually what I meant was implementing an XML-RPC and/or SOAP layer to support the ProxoolFacade. > > >>Might be a useful option to handle to support the switching of >>database URLs in failover situations on non-servlet solutions (i.e. >>bundle with the driver, and activate via XML or Properties). >> >> >We already allow switching of databases: either programmatically, or >with the upcoming JMX component or with the next version of >AdminServlet. If you mean _automatic_ switching then this is something >that Del Simmons has been talking about for a while. It would be really >cool and will probably be in 1.1. > > Now this would be cool. Acutally I again was referring that the XML-RPC and/or SOAP layers would be useful to manually redirect/switch over, but automatic is much cooler! > > >>Other thoughts is looking at other "delfacto" frameworks like Struts, >>Maverin, etc, and see what simple hooks we can provide to make >>integration seemless. >> >> >I know Struts quite well and I can't really think of anything we could >do that isn't already provided by the AdminServlet. We could produce a >Struts version of the AdminServlet (called, say, AdminAction) but it >would just end up duplicating AdminServlet. (Background: AdminServlet >does everything in a very simple way: HTML is coded in the Java class, >request parameters are extracted manually. All the things that would >make a servlet app a nightmare, and how we used to do it a long time >ago. However, because the scope of the servlet isn't very much, the >advantages we get in very simple configuration - no JSPs - outweigh >this, I believe.) > I agree lightweight is good aproach, I just threw Struts on the floor again because it's becoming a delfacto and the "tight integration" would be another sell feature. > >We do already provide an AvalonConfigurator. What's Maverin? > > I swear I ran across Maverin as another up-and-coming framework... but perhaps it was just a brain fart! I guess the overall idea is to find ways to make Proxool easily pluginable to any framework to make it more marketable. > > >>Also I've been using Hibernate (http://hibernate.sf.net) lately, and >>have contributed a little documentation and feedback on version 2.0 >>which is still in beta. Would be nice to provide a Proxool integration >>as one of the pool managers it would use. I'll look into maybe working >>on this. >> >> > >I'd be interested to learn how we can integrate with Hibernate. Doesn't >it just rely on any JDBC driver, or is it more complicated than that? > > Hibernate has built in a "non-production" ready pool manager. But for production it provides either pool manager hooks to use either c3po, DBCP or a DataSource (BTW this would be another good thing to support, but this is an old request I think). We would only need to implement this interface http://hibernate.bluemars.net/hib_docs/api/ and come up with a similar property passing solution as http://hibernate.bluemars.net/hib_docs/reference/html/session-configuration.html#session-configuration-s4. >3) Very good documentation. We're nearly there with this. Even closer >with DocBook. > > :) >My opinion is that we shouldn't try and squeeze much more into 1.0 and >we should plant our feet firmly in the ground and say "it's ready!". > > I fully agree, but you ask for the shopping list;) Although it would be good to have support for Hibernate 2.0 before it is release (there are no dates but I imagine soon). I feel it will probably become a high profile project with this release and it would be great "marketing" to be associated with it.... Ok off to the races on Docbook... Martin |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X