Menu
▾
▴
Re: [Proxool-developer] Staring with the doc pages
|
From: Abhishek M. <abh...@gm...> - 2009-04-14 06:19:26
|
If you guys want, I can attempt to port it to Github. On Fri, Apr 10, 2009 at 9:10 AM, Abhishek Manocha < abh...@gm...> wrote: > Cool Bill/Chris, > > That makes github and forking thing clearer. If I got it right, somebody > can have forked repository of proxool too hosted on it without effecting > main branch of proxool (even the documentation) if admin desire so and those > changes can be included easily too if admin desire so, right? > > The big point is still wiki, but going through github I got the impression > that it should be easy to set up and additional functionalities if we are > getting should not do any harm. I second for github, rest your call. > > On Thu, Apr 9, 2009 at 7:18 PM, < > pro...@li...> wrote: > >> Send Proxool-developer mailing list submissions to >> pro...@li... >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.sourceforge.net/lists/listinfo/proxool-developer >> or, via email, send a message with subject or body 'help' to >> pro...@li... >> >> You can reach the person managing the list at >> pro...@li... >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Proxool-developer digest..." >> >> >> Today's Topics: >> >> 1. Staring with the doc pages (Abhishek Manocha) >> 2. Re: Staring with the doc pages (Bill Horsman) >> 3. quick Clarification (Abhishek Manocha) >> 4. Configuring simultaneous-build-throttle and other >> (Abhishek Manocha) >> 5. house keeping sleep time (Abhishek Manocha) >> 6. Re: Staring with the doc pages (Christian Nedreg?rd) >> 7. Re: Staring with the doc pages (Bill Horsman) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 9 Apr 2009 11:09:17 +0530 >> From: Abhishek Manocha <abh...@gm...> >> Subject: [Proxool-developer] Staring with the doc pages >> To: pro...@li... >> Message-ID: >> <310...@ma...> >> Content-Type: text/plain; charset="iso-8859-1" >> >> >> hi All, >> >> Started using proxool and found some descrepencies in documentation to >> satrt >> with. Just for an example, AdminServlet fully qualifies location in the >> Configuration doc page is not right. That's not on wiki I presume and whom >> or how to get that corrected? Pointers? >> >> Abhishek Manocha >> -- >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 2 >> Date: Wed, 8 Apr 2009 22:47:19 -0700 >> From: Bill Horsman <bi...@lo...> >> Subject: Re: [Proxool-developer] Staring with the doc pages >> To: pro...@li... >> Message-ID: >> <9b1...@ma...> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Hello Abhishek, >> >> No it's not a Wiki but probably should be. I'm minded to move the whole >> project to Github - it allows a lot more collaboration through forking and >> the Wiki works well. Anyone have an opinion on that? >> >> - >> Bill >> >> 2009/4/8 Abhishek Manocha <abh...@gm...> >> >> >> > hi All, >> > >> > Started using proxool and found some descrepencies in documentation to >> > satrt with. Just for an example, AdminServlet fully qualifies location >> in >> > the Configuration doc page is not right. That's not on wiki I presume >> and >> > whom or how to get that corrected? Pointers? >> > >> > Abhishek Manocha >> > -- >> > >> > >> > >> ------------------------------------------------------------------------------ >> > This SF.net email is sponsored by: >> > High Quality Requirements in a Collaborative Environment. >> > Download a free trial of Rational Requirements Composer Now! >> > http://p.sf.net/sfu/www-ibm-com >> > _______________________________________________ >> > Proxool-developer mailing list >> > Pro...@li... >> > https://lists.sourceforge.net/lists/listinfo/proxool-developer >> > >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 3 >> Date: Thu, 9 Apr 2009 12:09:48 +0530 >> From: Abhishek Manocha <abh...@gm...> >> Subject: [Proxool-developer] quick Clarification >> To: pro...@li..., >> pro...@li... >> Message-ID: >> <310...@ma...> >> Content-Type: text/plain; charset="iso-8859-1" >> >> hi, >> >> Will using >> <init-param> >> <param-name>autoShutdown</param-name> >> <param-value>true</param-value> >> </init-param> >> >> in Servletconfigurator (or letting it default true) >> remove all the proxool pools may be used by other web applications also in >> same web server. Can't help, documentation was ambiguous at that point. >> >> And the second more important one, how can I make sure that >> Servletconfigurator is the last one to get destroyed and so the pools >> remain >> active in my web app. My scenarios is that I have 4-5 servlets all getting >> connection from the same pool, I want to make it absolute that >> pool remains there through ServletConfigurator even if the service of >> other >> servlets is not called for a considerable amount of time >> >> --Abhishek Manocha >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 4 >> Date: Thu, 9 Apr 2009 12:41:32 +0530 >> From: Abhishek Manocha <abh...@gm...> >> Subject: [Proxool-developer] Configuring simultaneous-build-throttle >> and other >> To: pro...@li..., proxool-user >> <pro...@li...> >> Message-ID: >> <310...@ma...> >> Content-Type: text/plain; charset="iso-8859-1" >> >> how can i configure >> >> simultaneous-build-throttle: >> maximum-connection-lifetime: >> maximum-active-time: >> >> in proxool through proxool.xml or the or web.xml? >> i mean should it go in init-param of Servletconfigurator or the >> proxool.xml >> configuration? >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 5 >> Date: Thu, 9 Apr 2009 13:33:01 +0530 >> From: Abhishek Manocha <abh...@gm...> >> Subject: [Proxool-developer] house keeping sleep time >> To: pro...@li..., proxool-user >> <pro...@li...> >> Message-ID: >> <310...@ma...> >> Content-Type: text/plain; charset="iso-8859-1" >> >> in case of scenario of where 10 connections need to be maintained in the >> pool, >> what should be the simultaneous-build-throttle and >> house-keeping-sleep-time >> in other words what these parameters are for? >> Does housekeeping threads make connection to db in that case shouldn't I >> be >> keeping that high instead of 30s default? >> >> Regarding AdminServlet provided for checking out the bottleneck of the >> connection, I am getting weird connections created at 30 40 secs or so >> in lots of 2, 3 or 4 connections created at same time, my code is not >> creating any such connections so the AdminServlet has complicated the >> matter >> instead of solving. >> Can you guys please help me in letting me know how to debug and check >> which >> connections are not getting released through AdminServlet >> >> Thanks >> --Abhishek >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 6 >> Date: Thu, 9 Apr 2009 15:17:02 +0200 >> From: Christian Nedreg?rd <chr...@em...> >> Subject: Re: [Proxool-developer] Staring with the doc pages >> To: Pro...@li... >> Message-ID: >> <fe7...@ma...> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Hi. >> >> Long time no hear :) >> >> I haven't familiarized myself with Git yet. Could you elaborate a bit on >> what you mean by "collaboration through forking" and why that is >> desirable? >> >> In my opinion a Wiki is fine for HOWTOs and other secondary documentation, >> but I think it's better to keep the formal documentation under version >> control to keep it under adequate quality control and in sync with the >> version the user actually are using. >> >> Christian >> >> On Thu, Apr 9, 2009 at 7:47 AM, Bill Horsman <bi...@lo... >> >wrote: >> >> > Hello Abhishek, >> > >> > No it's not a Wiki but probably should be. I'm minded to move the whole >> > project to Github - it allows a lot more collaboration through forking >> and >> > the Wiki works well. Anyone have an opinion on that? >> > >> > - >> > Bill >> > >> > 2009/4/8 Abhishek Manocha <abh...@gm...> >> >> > >> >> hi All, >> >> >> >> Started using proxool and found some descrepencies in documentation to >> >> satrt with. Just for an example, AdminServlet fully qualifies location >> in >> >> the Configuration doc page is not right. That's not on wiki I presume >> and >> >> whom or how to get that corrected? Pointers? >> >> >> >> Abhishek Manocha >> >> -- >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> This SF.net email is sponsored by: >> >> High Quality Requirements in a Collaborative Environment. >> >> Download a free trial of Rational Requirements Composer Now! >> >> http://p.sf.net/sfu/www-ibm-com >> >> _______________________________________________ >> >> Proxool-developer mailing list >> >> Pro...@li... >> >> https://lists.sourceforge.net/lists/listinfo/proxool-developer >> >> >> >> >> > >> > >> > >> ------------------------------------------------------------------------------ >> > This SF.net email is sponsored by: >> > High Quality Requirements in a Collaborative Environment. >> > Download a free trial of Rational Requirements Composer Now! >> > http://p.sf.net/sfu/www-ibm-com >> > _______________________________________________ >> > Proxool-developer mailing list >> > Pro...@li... >> > https://lists.sourceforge.net/lists/listinfo/proxool-developer >> > >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 7 >> Date: Thu, 9 Apr 2009 06:48:49 -0700 >> From: Bill Horsman <bi...@lo...> >> Subject: Re: [Proxool-developer] Staring with the doc pages >> To: Christian Nedreg?rd <chr...@em...> >> Cc: Pro...@li... >> Message-ID: >> <9b1...@ma...> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Hei Christian! >> >> Good to hear from you :) >> >> Actually, as soon as I sent that last message I realised that I should >> have >> been clearer and not confused a Wiki with forking. Let me deal with each >> of >> those in turn: >> >> GitHub is an obvious place to host a Git repository. It gives you a Wiki >> that makes it much easier to maintain the documentation. The Wiki is only >> editable by designated collaborators (equivalent to the small group of >> committers we have at SourceForge). It's not the only solution by far but >> it's much easier to change than the present documentation which is just >> static HTML. I'm approaching this from the aspect of that there needs to >> be >> almost zero developer effort since I'm not aware of anyone having time to >> work on this. Copy and pasting from the current website into GitHub Wiki >> would be relatively easy. >> >> If anyone is prepared to put the effort in, getting the documentation >> under >> source control would be wonderful. It isn't at the moment. I'm open to any >> suggestions. >> >> As to "collaboration through forking", Git makes it simple (even >> desirable) >> for external collaborators (ones that we haven't chosen or selected in any >> way) to fork the project and make their own changes as they see fit. Git >> also makes it simple to pull those changes back into the master repository >> (in a controlled way). The whole thing is much more democratic with each >> commit making it back into the project on its own merits. >> >> - >> Bill >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> High Quality Requirements in a Collaborative Environment. >> Download a free trial of Rational Requirements Composer Now! >> http://p.sf.net/sfu/www-ibm-com >> >> ------------------------------ >> >> _______________________________________________ >> Proxool-developer mailing list >> Pro...@li... >> https://lists.sourceforge.net/lists/listinfo/proxool-developer >> >> >> End of Proxool-developer Digest, Vol 11, Issue 1 >> ************************************************ >> > > |
