Re: best practie for open and close connection database

2010-04-21 Thread Felipe de Jesús Molina Bravo
El 21 de abril de 2010 17:33, Chris Bennett escribió: > On 04/21/10 11:33, Felipe de Jesús Molina Bravo wrote: > >> Hi >> >> In my application, I opened my database from authentication handler and >> close it from child exit handler. It is correct (is a best practice)? or >> is a bad design? >> >>

Re: Pre-processing the request body

2010-04-21 Thread Michael Ludwig
Am 21.04.2010 um 18:57 schrieb Jeff McCarrell: > If you are the type that likes to buy books, let me give a shout out to _ > mod_perl 2 User's Guide _ by Stas Bekman and Jim Brandt. I think it's almost identical to the online version: http://perl.apache.org/docs/2.0/user/index.html > I notice C

Re: Pre-processing the request body

2010-04-21 Thread Jeff McCarrell
Hey John If you are the type that likes to buy books, let me give a shout out to _ mod_perl 2 User's Guide _ by Stas Bekman and Jim Brandt. It has helped me a lot to leverage the power available in mp2. I notice Ch 6 of that book: Input and Output filters, with subsections: I/O Filtering Concep

Re: best practie for open and close connection database

2010-04-21 Thread Chris Bennett
On 04/21/10 11:33, Felipe de Jesús Molina Bravo wrote: Hi In my application, I opened my database from authentication handler and close it from child exit handler. It is correct (is a best practice)? or is a bad design? where i can read for best practice for it? thank's Are you using Apach

Re: best practie for open and close connection database

2010-04-21 Thread Michael Peters
On 04/21/2010 12:33 PM, Felipe de Jesús Molina Bravo wrote: In my application, I opened my database from authentication handler and close it from child exit handler. It is correct (is a best practice)? or is a bad design? Typically it's best practice to not close DB handles. That's why Apache

best practie for open and close connection database

2010-04-21 Thread Felipe de Jesús Molina Bravo
Hi In my application, I opened my database from authentication handler and close it from child exit handler. It is correct (is a best practice)? or is a bad design? where i can read for best practice for it? thank's

Re: non-stop generational modperl config update strategies?

2010-04-21 Thread Torsten Förtsch
On Wednesday 21 April 2010 17:19:22 Perrin Harkins wrote: > 2010/4/21 Torsten Förtsch : > > no, MMapDB creates read-only variables that reference the mmapped block. > > It manipulates SvPVX directly > > Very interesting! I'll have to try it out as a storage backend for CHI. One really cool thing

Re: non-stop generational modperl config update strategies?

2010-04-21 Thread Cosimo Streppone
On Wed, 21 Apr 2010 17:10:00 +0200, Torsten Förtsch wrote: On Wednesday 21 April 2010 16:59:01 Perrin Harkins wrote: In both cases you have the same drawback: it's impossible to read anything from the shared data without copying the data you read into perl variables. [...] no, MMapDB create

Re: non-stop generational modperl config update strategies?

2010-04-21 Thread Perrin Harkins
2010/4/21 Torsten Förtsch : > no, MMapDB creates read-only variables that reference the mmapped block. It > manipulates SvPVX directly Very interesting! I'll have to try it out as a storage backend for CHI. - Perrin

Re: non-stop generational modperl config update strategies?

2010-04-21 Thread Torsten Förtsch
On Wednesday 21 April 2010 16:59:01 Perrin Harkins wrote: > In both cases you have the same drawback: it's impossible to read > anything from the shared data without copying the data you read into > perl variables. A shared database only saves memory if you don't need > all of the data to handle a

Re: non-stop generational modperl config update strategies?

2010-04-21 Thread Perrin Harkins
2010/4/21 Torsten Förtsch : > The mmapdb databases (single files) can be prepared off-line and then be > copied to the destination. Then the old database (still mapped by its users) > is invalidated by setting a flag. At the time of the next access the new > version will be mmapped. MMapDB is compl

Pre-processing the request body

2010-04-21 Thread John ORourke
Hi folks, I have a mod-perl app on the receiving end of a POST from a credit card company, and they are sending the data as application/x-www-form-urlencoded but they aren't URL-encoding UTF-8 characters. When I give that malformed data to Apache2::Request it refuses to see any POST variables ata

Re: How to handle long running requests without locking an apache worker

2010-04-21 Thread Michael Ludwig
Am 19.04.2010 um 17:58 schrieb Torsten Förtsch: > http://foertsch.name/ModPerl-Tricks/req-hand-over.shtml Quoting from this page: "One note at first, by the time of this writing the released modperl version is not able to do this by the reason that there is no interface to fetch the client sock

Re: How to handle long running requests without locking an apache worker

2010-04-21 Thread Tosh Cooey
This will become very important as the PUSH capability of HTML5 gains traction. Maybe I should go read it again :) Thanks Torsten! Tosh Torsten Förtsch wrote: Hi, some of you might find this one interesting: http://foertsch.name/ModPerl-Tricks/req-hand-over.shtml Torsten Förtsch -- M

Re: non-stop generational modperl config update strategies?

2010-04-21 Thread Torsten Förtsch
On Wednesday 21 April 2010 02:18:33 Jeff McCarrell wrote: > I am willing to trade memory and CPU to achieve a non-stop apache instance. > > So modperl experts: any pointers on prior art here? > I'd love to hear about strategies that have been shown to work in real > life. > I use Apache2::Transl