RE: Query relating to Apache::ASP

You might also try ChiliSoft to see what they can do to help you. They have a product that allows ASP code to run under apache. I think there is one other company that does something similar though the name escapes me.     -Original Message- From: Ranjeet [mailto:[EMAIL PROTECTE

RE: Storable not working under Embperl?

So it seems that there is something that EmbPerl is putting into the data that is going to storable that is a GLOB, code, and other stuff. Any ideas Gerald? -Original Message- From: Scott Chapman [mailto:[EMAIL PROTECTED]] Sent: Monday, March 18, 2002 5:55 PM To: Cross, Patrick Cc: [E

RE: Storable not working under Embperl?

Even though the man page states that a meaningless string is stored, we haven't found that "real" data (numbers, strings, hashes) are getting lost. Try setting the forgive_me and test to make sure your data is coming back correctly. -Original Message- From: Scott Chapman [mailto:[EMAIL

RE: Storable not working under Embperl?

You can also set $Storable::forgive_me=1; and you'll still get the warning but no error. We found that if we used function references in some places this would pop up. -Original Message- From: Gerald Richter [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 8:49 AM To: S

RE: 2 more embperl2 oddities - Execute

The extra new can cause issues, especially with non-html data. As an example, if you have a page with some sort of generic authentication check at the top (via execute), and then you get some data (say an RTF file) from a database or file. If you send the RTF data back to the client the newline at

RE: persistent DBI conncetions

You can try looking at Apache::DBI. It supports connection pooling. -Original Message- From: Bjoern [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 01, 2001 9:05 AM To: [EMAIL PROTECTED] Subject:persistent DBI conncetions Hi all, does anyone know if the DBI interface in

RE: Caching question

We are seeing a larger memory leak in our application, and think it may be from the DBI layer or our use of it. We tried using Apache:leak, but are not sure if that works well with embperl - is that the best thing to use for tracking down the leaks? Also, "top" works well for monitoring the memor

RE: Apache mod_perl gets blinded (@INC)

We finally gave up and put a symlink in apache/lib/perl that pointed to our modules directory. Apache seems to always look there regardless. -Original Message- From: Neeme Vool [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 2:41 AM To: [EMAIL PROTECTED] Subject: