Hi,
I've compiled and installed Apache httpd 2.0.55 on HP-UX 11.11 in 64bit
mode. The compilation of mod_perl 2.0.2 needed some tweaks (i.e., I had to
remove the "+DD64" flag from the LDFLAGS lines in all Makefiles because ld
doesn't like it) but after all it compiles without problems. Unfortunate
Hi,
Currently we have
package Apache::RegistryLexInfo;
@ISA = qw(Apache::RegistryNG);
Should the next version which supports mod_perl 1.x and 2.x:
o sub class ModPerl::RegistryBB, ModPerl::RegistryPrefork,
ModPerl::Registry ?
o Should it be configurable via a d
I am just getting introduced to mod-perl. Can anyone point me in a direction
for learning this from scratch?
I have experience in VB6, VB.NET, VC+. I do not know anything about Perl,
PerlScript, or mod_perl. I would like to start with the basics and learn
syntax.
Any help would be greatly appreci
I am just getting introduced to mod-perl. Can anyone point me in a
direction
for learning this from scratch?
I have experience in VB6, VB.NET, VC+. I do not know anything about Perl,
PerlScript, or mod_perl. I would like to start with the basics and learn
syntax.
Any help would be greatly app
Badai Aqrandista wrote:
I am just getting introduced to mod-perl. Can anyone point me in a
direction
for learning this from scratch?
I suggest your look at the things mentioned in
perldoc perl
Also,
for mod_perl
http://perl.apache.org
is very well done (I'm just slightly biased)
--
--
Hi All,
I am experiencing intermittently missing session data. After weeks of
investigation, we suspect the size of the data we put in the session as the
culprit: it is too big. So I am trying to fix it by adding Storable hooks
for objects stored in the session to create smaller serialized dat
On Wed, 2005-11-30 at 14:29 +1000, Badai Aqrandista wrote:
> I am experiencing intermittently missing session data. After weeks of
> investigation, we suspect the size of the data we put in the session as the
> culprit: it is too big.
What database are you using? I thought the default data type
Hi Perrin,
What database are you using? I thought the default data types for most
of them would hold a very large amount of data before having trouble. I
suspect you are having locking problems or session data is not being
written because the session object doesn't go out of scope.
I am usin
On Wed, 2005-11-30 at 15:23 +1000, Badai Aqrandista wrote:
> I am using MySQL 4.1 on debian sarge. The type of the field that hold the
> session data is 'longtext'.
That holds a very large amount of data. You can't be overflowing that.
> Patrick Michaud pointed me off the list that i
> should
