understand the theory to work anyway.
Josh
[EMAIL PROTECTED]
08/20/2002 10:54 AM
To: Tony Bowden [EMAIL PROTECTED], md [EMAIL PROTECTED]
cc: Perrin Harkins [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject:Re: Apache::Session - What goes in session?
We do see
to it. Or at least
that's how I
understand the theory to work anyway.
Josh
[EMAIL PROTECTED]
08/20/2002 10:54 AM
To: Tony Bowden [EMAIL PROTECTED], md
[EMAIL PROTECTED]
cc: Perrin Harkins [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject:Re: Apache
Not in the MS house that I am living in right now :^(
On Tue, 20 Aug 2002, Perrin Harkins wrote:
Ian Struble wrote:
And just to throw one more wrench into the works. You could load up only
the most popular data at startup and let the rest of the data get loaded
on a cache miss.
I'm using mod_perl and Apache::Session on an app that
is similar to MyYahoo. I found a few bits of info from
a previous thread, but I'm curious as to what type of
information should go in the session and what should
come from the database.
Currently I'm putting very little in the session
Hello md --
I'm using mod_perl and Apache::Session on an app that
is similar to MyYahoo. I found a few bits of info from
a previous thread, but I'm curious as to what type of
information should go in the session and what should
come from the database.
One thing to watch out for is the trap
md wrote:
Currently I'm putting very little in the session
Good. You should put in as little as possible.
what I am putting in the session is more global in
nature...greeting, current page number, current page
name...
That doesn't sound very global to me. What happens when users open
Thanks though. That was succinctly put.
Could you go back in time and tell me that a year or two ago?
That would be great, thanks again.
-Josh
:)
Things like the login status of this session,
and the user ID that is associated with it go
in the session. Status of a particular page
has
caching. Don't use the session for
caching, use a cache for
it. They're not the same. A session is often
stored in a database so
that it can be reliable. A cache is usually stored
on the file system
so it can be fast.
The session is stored in a database
(Apache::Session::MySQL), and I
you're doing
with Apache::Session for the things you referred to as global. There
are also good examples in the documentation for the Memoize module.
There are various reasons to use a cache rather than treating the
session like a cache. If you put a lot of data in the session, it will
slow down
with Apache::Session for the things you referred to
as global. There
are also good examples in the documentation for the
Memoize module.
Great...exactly the kind of info I was looking for.
I'll look at those. We are using a load-balanced
system; I shoudl have mentioned that earlier. Won't
system. Unfortunately, the Apache::Session code isn't all that
easy to use for this, since it assumes you want to generate IDs for the
objects you store rather than passing them in. You could adapt the code
from it to suit your needs though. The important thing is to leave out
all
Hi, I'm in major poop.
Got a presentation soon and my just implemented, implementation of
Apache::Session is not working as per the man page.
I've set commit to 1 and tied a session to a postgres database. I then
set a field and check the table it's not there.
When I later do a fetch on it, I
What does your config file look like? All pointing at the right tables
and fields and such?
-Fran
Rafiq Ismail (ADMIN) wrote:
Hi, I'm in major poop.
Got a presentation soon and my just implemented, implementation of
Apache::Session is not working as per the man page.
I've set commit to 1
Wait, ignore that - I was getting my Apache::Session and my
Apache::AuthCookie signals crossed. Sorry.
-Fran
Fran Fabrizio wrote:
What does your config file look like? All pointing at the right
tables and fields and such?
-Fran
Rafiq Ismail (ADMIN) wrote:
Hi, I'm in major poop
Subject: Apache::Session HELP!
Sent by: Rafiq
Ismail (ADMIN)
rafiq
Just 8 lines of glue code to use YAML as a Apache::Session
serialization handler. Any suuggestions welcome, Thanks.
The URL
http://bulknews.net/lib/archives/Apache-Session-Serialize-YAML-0.01.tar.gz
has entered CPAN as
file: $CPAN/authors/id/M/MI/MIYAGAWA/Apache-Session-Serialize-YAML
Hi,
I would like to implement sessions using only $ENV{REMOTE_USER} as the
session key as described on page 259 (Ch. 5) of the Eagle book.
I'm trying to use Apache::Session::MySQL. Since I'm generating my own
session key outside of Apache::Session (using $ENV{REMOTE_USER}), what
method(s) do I
Perrin Harkins wrote:
Brian Parker wrote:
I'm trying to use Apache::Session::MySQL. Since I'm generating my own
session key outside of Apache::Session (using $ENV{REMOTE_USER}), what
method(s) do I have to override to prevent Apache::Session from trying
to create a session key for me
I was attempting to store a blessed object via Apache::Session, but
when the session is returned, the hash is empty. I did some google
searching and ran across a similar question:
http://www.geocrawler.com/archives/3/182/2000/5/0/3823715/
I have not found any other information
On Tue, 2002-05-21 at 16:16, [EMAIL PROTECTED] wrote:
I was attempting to store a blessed object via Apache::Session, but
when the session is returned, the hash is empty. I did some google
searching and ran across a similar question:
http://www.geocrawler.com/archives/3/182/2000/5/0
On Tue, 2002-05-21 at 19:19, [EMAIL PROTECTED] wrote:
Chris Winters writes:
Nothing special should be required -- I've done this with no problem
using recent versions -- 1.50+ -- of Apache::Session. The only way it
might be a problem is if you're trying to save a special resource
You need to do some more debugging. Problems with Apache::Session are
usually due to scoping, so put in some debug statements to see that the
session objects for the IDs having trouble are getting properly cleaned
up (i.e. DESTROY is getting called). It is possible to have problems
You need to do some more debugging. Problems with Apache::Session are
usually due to scoping, so put in some debug statements to see that the
session objects for the IDs having trouble are getting properly cleaned
up (i.e. DESTROY is getting called). It is possible to have problems
Stathy G. Touloumis wrote:
You need to do some more debugging. Problems with Apache::Session are
usually due to scoping, so put in some debug statements to see that the
session objects for the IDs having trouble are getting properly cleaned
up (i.e. DESTROY is getting called). It is possible
On Mon, 29 Apr 2002, F. Xavier Noria wrote:
3. Could one set up things in a way that allows the database to see
the timestamps and program a trigger to delete old sessions? Or
is there a standard idiom for doing this in a different way?
thats what i usually do ...
If I understand it correctly, Apache::Session::Oracle uses a table
called sessions with at least two columns, one called id, of type
varchar2(32), and another called a_session, of type long.
Say I want to store a pair of things in sessions: a reference to an
object of type User (which includes
If I understand it correctly, Apache::Session::Oracle uses a table
called sessions with at least two columns, one called id, of type
varchar2(32), and another called a_session, of type long.
Say I want to store a pair of things in sessions: a reference to an
object of type User (which includes
If I understand it correctly, Apache::Session::Oracle uses a table
called sessions with at least two columns, one called id, of type
varchar2(32), and another called a_session, of type long.
Say I want to store a pair of things in sessions: a reference to an
object of type User (which includes
On Mon, 29 Apr 2002 01:11:59 +0200
F.Xavier Noria [EMAIL PROTECTED] wrote:
: If I understand it correctly, Apache::Session::Oracle uses a table
: called sessions with at least two columns, one called id, of type
: varchar2(32), and another called a_session, of type long.
I am sorry
Sorry if this is already known, or if I'm posting to the wrong
people, (I'm new to the mod_perl world), but :
Looks like there's a minor bug in Apache::Session::Lock::File::clean().
Patch : (against version 1.01, in distribution Apache-Session-1.54)
(also adding proper local()ization of handles
Has anyone ever thought to have the table name modifiable? E.g. instead of
'sessions', you could set it to something like 'preferences' for a given
instance. I wanted to maintain session information, but also preferences
that are attached to a given username. I could just put the two within
and contexts can pass from session to session.
Basically break identity apart from process. Apache::Session would
be ideal for both since the storage mechanisms are identical.
Unfortunately, the table name is hard-coded.
--
James Smith [EMAIL PROTECTED], 979-862-3725
Texas AM CIS Operating Systems Group
I once did a one-off mod of Apache::Session to do just
this but eventually gave up and just changed my table
names. It was to hard to keep in sync with new releases of
Apache::Session and I don't have enough faith in my
ability to send a real patch :)
So I think its a natural path. When you
Hi Jeffrey,
I've found a bug in clean method of Apache::Session::Lock::File when check
lockfiles last access time.
In effects the result of expression:
(stat($dir.'/'.$file))[8] - $now
is always negative and lock dir cleanup isn't done.
The patch simply inverts the check.
Bye
On Mon, 2002-03-25 at 15:44, Stathy G. Touloumis wrote:
Has anyone ran into issues with data being written to the data source using
Apache::Session::Store::DB_File and Apache::Session::Lock::File? We are
running into a unique instance where a value is not being saved to the
session store
get a 'false' value returned which
I cannot figure out why.
Has anyone ran into issues with data being written to the data
source using
Apache::Session::Store::DB_File and Apache::Session::Lock::File? We are
running into a unique instance where a value is not being saved to the
session
Announcing the update of PHP::Session and yet another module of nightmare.
You can download 'em from http://bulknews.net/lib/archives/ and CPAN.
NAME
Apache::Session::PHP - glues Apache::Session with PHP::Session
SYNOPSIS
use Apache::Session::PHP;
tie %session, 'Apache
Has anyone ran into issues with data being written to the data source using
Apache::Session::Store::DB_File and Apache::Session::Lock::File? We are
running into a unique instance where a value is not being saved to the
session store at a certain point through a workflow. There are multiple
I am trying to install Apache::Session and it is failing on
the DBD::Oracle tests. It is asking for a default user. Do
I need to configure Oracle for a default user? Or do I need
to set some environment variable with a user id and password?
brian
Here are the errors I am getting:
t/99oracle
Brian Lavender wrote:
I am trying to install Apache::Session and it is failing on
the DBD::Oracle tests. It is asking for a default user. Do
I need to configure Oracle for a default user? Or do I need
to set some environment variable with a user id and password?
well, looking at t
On Mon, 11 Mar 2002, Brian Lavender wrote:
Date: Mon, 11 Mar 2002 11:24:35 -0800
From: Brian Lavender [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Apache::Session problem with DBD::Oracle
I am trying to install Apache::Session and it is failing on
the DBD::Oracle tests. It is asking
trying to install Apache::Session and it is failing on
the DBD::Oracle tests. It is asking for a default user. Do
I need to configure Oracle for a default user? Or do I need
to set some environment variable with a user id and password?
well, looking at t/99oracle.t (line 45) it looks like
:
I am trying to install Apache::Session and it is failing on
the DBD::Oracle tests. It is asking for a default user. Do
I need to configure Oracle for a default user? Or do I need
to set some environment variable with a user id and password?
well, looking at t/99oracle.t (line
I am trying to test the Apache::Session::Oracle
Here is the error I am getting. What is wrong? I was able to
successfully install and test Apache::Session which tested
Apache::Session::Oracle
This is the error.
[Mon Mar 11 14:01:23 2002] [error] Can't locate object method TIEHASH via package
On Mon, Mar 11, 2002 at 02:08:10PM -0800, Brian Lavender wrote:
I am trying to test the Apache::Session::Oracle
Here is the error I am getting. What is wrong? I was able to
successfully install and test Apache::Session which tested
Apache::Session::Oracle
This is the error.
[Mon Mar
Title: Apache::Session problems
Hello,
I am trying to use Apache::Session to store http session information.
The version number of Apache::Session is 1.54. It is running on Apache/1.3.20 (Unix) mod_perl/1.26 configured.
I am using the TicketTool from the o'reilly book, I make a tie
On Thu, 2002-02-28 at 06:16, Domien Bakker wrote:
Hello,
I am trying to use Apache::Session to store http session information.
The version number of Apache::Session is 1.54. It is running on
Apache/1.3.20 (Unix) mod_perl/1.26 configured.
...
Both methods resolve to the same error
, at
/usr/local/lib/perl5/site_perl/5.6.1/Apache/Session/Serialize/Storable.p
m line 27
CW This sounds like someone with a more recent version of Storable
CW in their private lib has been testing sessions or something,
CW since there's a mismatch of what is in the database
As an add-on to this, does anyone know if one could use MySQL HEAP
(memory resident) tables for the session table?
--Jon Robison
Rob Bloodgood wrote:
I am using Apache::Session with Postgresql. Unfortunately I had
never worked with a huge amount of data before I started to program
I am using Apache::Session with Postgresql. Unfortunately I had
never worked with a huge amount of data before I started to program
something like a (little) web application. I happily packed
everything in the session(s-table) that might be of any use. It
hit me hard that it takes
Hi Milo,
thanks for your answer. I hope you will excuse, but I am not sure
whether I got you right.
The session hash is serialized/deserialized in its entirety using the
Storable module.
Does this mean, that - after tying the session hash - it is of no importance
(concerning the amount of time
On Sun, 2002-02-24 at 02:43, Christoph Lange wrote:
Hi Milo,
thanks for your answer. I hope you will excuse, but I am not sure
whether I got you right.
The session hash is serialized/deserialized in its entirety using the
Storable module.
Does this mean, that - after tying the session
to take apart the various Apache::Session modules and see
what makes them tick.
--
Milo Hyson
CyberLife Labs, LLC
Hi,
I guess that thisis going to be another
"what-a-bloody-beginner"-question
but I hope somebody will be in a good mood and help
me out.
I am using Apache::Session with Postgresql.
Unfortunately I had never worked with a huge
amount of data
before I started to program some
On Saturday 23 February 2002 03:03 pm, Christoph Lange wrote:
Hi,
I guess that this is going to be another what-a-bloody-beginner-question
but I hope somebody will be in a good mood and help me out.
I am using Apache::Session with Postgresql. Unfortunately I had never
worked with a huge
PROTECTED]
Sent: Friday, January 18, 2002 1:53 AM
Subject: Re: Apache::Session getting DESTROYed in wrong order
On Friday, January 18, 2002, at 12:44 AM, Perrin Harkins wrote:
In a Mason context, which is where I'm using it, I do this in my
top-level autohandler (ignore the main:: subroutines
I register a clean up handler to explicitly untie the session variable.
I have found that it's safer to put things in pnotes than to use globals and
cleanup handlers. We used a lot of cleanup handlers at eToys to clear
globals holding various request-specific things, and we started getting
I've been told this is the place to send questions related to apache perl
modules.
I believe I have discovered a locking bug in Apache::Session::File.
The following code should retrieve an existing session from the file system
and place an exclusive lock on the session file:
my $locking_args
On Friday, January 4, 2002, at 02:22 AM, Ken Williams wrote:
For the sake of thread completion, here's a script which demonstrates
the bug. It turns out to be a Perl bug (5.6.1, at least), not an
Apache::Session bug. I'll post to p5p after I post here.
I was surprised to find the it's
('_session_id');
tie %session, 'Apache::Session::MySQL', $session_id,
{Handle = $dbh, LockHandle = $dbh};
...
/%init
Geez, that's awfully confusing to look at (local and typeglobs is not a
newbie-friendly combo). Isn't there a simpler way? What about putting
it in pnotes
*session;
my $dbh = ::get_dbh;
my $session_id = ::get_cookie('_session_id');
tie %session, 'Apache::Session::MySQL', $session_id,
{Handle = $dbh, LockHandle = $dbh};
...
/%init
Geez, that's awfully confusing to look at (local and typeglobs is not a
newbie-friendly combo
Hey,
For the sake of thread completion, here's a script which demonstrates
the bug. It turns out to be a Perl bug (5.6.1, at least), not an
Apache::Session bug. I'll post to p5p after I post here.
Note that $foo and %bar are cleaned up by refcount, but %foo isn't
cleaned up until global
# Won't get cleaned up properly
local %foo;
tie %foo, 'Dummy', name = '%foo';
local only make a copy of the original value and restores it at the end of
the scope, so %foo will not destroyed, but restored at the end of the scope.
I guess this is the reason my it still stays tied.
In
On Friday, January 4, 2002, at 02:48 AM, Gerald Richter wrote:
# Won't get cleaned up properly
local %foo;
tie %foo, 'Dummy', name = '%foo';
local only make a copy of the original value and restores it at the end
of
the scope, so %foo will not destroyed, but restored at the end
Hi Aaron,
I don't have a test case involving Apache::Session yet (I've been out of
town for a couple days), but here's a simple one in Perl that
demonstrates the DESTROY order problem:
--
#!/usr/bin/perl
{
package Outer;
sub
On Thursday, January 3, 2002, at 11:57 AM, Perrin Harkins wrote:
I don't have a test case involving Apache::Session yet (I've been out
of
town for a couple days), but here's a simple one in Perl that
demonstrates the DESTROY order problem:
That's sort of a weird example, since it has
The circular reference was the only way I could think of to force an
object to be destroyed during global destruction.
What happens if you use a global?
Hmm, that may be - Mason does create more closures now than it used to.
It seems like only 'named' closures would create this problem,
On Mon, 31 Dec 2001, Ken Williams wrote:
Hey,
I'm having problems with Apache::Session, the symptom is that none of my
data is getting written to the database. It's not the nested-data
problem, since I'm not using any nested data structures.
After some investigation, I've discovered
On Thursday, January 3, 2002, at 02:02 PM, Jeffrey W. Baker wrote:
This seems like a really weird problem. The Store module is destroyed
while another module still has a reference to it. Unfortunately for you
and I, the only conclusion I have been able to draw is that Perl's
DESTROY
Hi Ken,
refcount destruction. I've declared %session as a locally-scoped
variable, so it should evaporate before global destruction, unless it's
got circular data structures or something. Anyone know what might be
going on?
Do you have a simple case we can test yet?
Aaron
Hey,
I'm having problems with Apache::Session, the symptom is that none of my
data is getting written to the database. It's not the nested-data
problem, since I'm not using any nested data structures.
After some investigation, I've discovered that the
Apache::Session::Store::MySQL::DESTROY
I have been beating my head against this problem for days, to no avail.
I have tried google searches, etc., still no dice. So, I apologize for
the noise people.
I'm using Apache::Session and cookies to perform session management. In
watching the debug messages in my error_log, I can see
Just to let anyone who was wondering (and for the benefit of the archives),
I ended up ditching sessions all together. Instead, I'm using
Apache::AuthDBI to do authentication, and am making calls directly to my
database server to maintain state. Its not the most pleasant way of
maintaining
.
- Not using the locking API correctly. You didn't post any code, but
the locking options for Apache::Session sometimes trip people up and you
may have had a misconfiguration of some kind.
Anyway, there's nothing wrong with writing directly to the database.
Apache::Session is just a convenient
I have been beating my head against this problem for days, to no avail.
I have tried google searches, etc., still no dice. So, I apologize for
the noise people.
I'm using Apache::Session and cookies to perform session management. In
watching the debug messages in my error_log, I can see
to load the session. Occasionally, one of them successfully loads the
original session, but the other two end up creating their own sessions.
When I call:
tie %session, 'Apache::Session::Flex', $id, \%options;
it doesn't return anything in $@, except there is no data inside
%session
At 3:06 PM -0800 12/5/01, Michael A Nachbaur wrote:
I have been beating my head against this problem for days, to no
avail. I have tried google searches, etc., still no dice. So, I
apologize for the noise people.
I'm using Apache::Session and cookies to perform session management
Hi Michael -
I'm using Apache::Session and cookies to perform session management. In
watching the debug messages in my error_log, I can see that the cookie
is created, the session is created, and all subsequent calls correctly
loads the session. However, part of the design for my web
: Re: Apache::Session and frames
At 3:06 PM -0800 12/5/01, Michael A Nachbaur wrote:
I have been beating my head against this problem for days, to no
avail. I have tried google searches, etc., still no dice. So, I
apologize for the noise people.
I'm using Apache::Session and cookies to perform
On Thu, 22 Nov 2001, Jonathan M. Hollin wrote:
My code now includes:
35: # Session handler...
36: my %session; undef my $session_id;
37: use Apache::Session::MySQL;
38: tie %session, 'Apache::Session::MySQL', $session_id,
39: { DataSource = 'dbi:mysql:sessions', UserName = 'db_user
Thank you everyone for the quality of help I've so far received and your
rapid responses. However... :-(
My code now includes:
35: # Session handler...
36: my %session; undef my $session_id;
37: use Apache::Session::MySQL;
38: tie %session, 'Apache::Session::MySQL', $session_id,
39
there. This accompanies the book
for which the aforementioned URL is the home site. Said
book has a chapter on sessions focusing on Apache::Session,
so you may find the example scripts useful for helping
you solve your problem.
My code now includes:
35: # Session handler...
36: my %session; undef
Fellow Perl Mongers,
Can anyone help with my latest programming riddle?
I am trying to take advantage of the session-handling features of
Apache::Session. My program includes the following code (line numbers added
for clarity):
20: # Session handler (I)...
21: use Apache::Session::DBI;
[cut
On Wed, 21 Nov 2001 22:49:46 -, Jonathan M. Hollin
[EMAIL PROTECTED] said:
Jonathan Fellow Perl Mongers,
Jonathan Can anyone help with my latest programming riddle?
Jonathan I am trying to take advantage of the session-handling
Jonathan features of Apache::Session. My program includes
Thanks to Ilya Martynov for his response...
I changed Apache::Session::DBI to Apache::Session::MySQL and tried
again. The following error graced my error log:
[Wed Nov 21 23:01:13 2001] [error] PerlRun: `Died at
E:/Apache/site/lib/Apache/Session/Generate/MD5.pm line 40.'
Looking at MD5.pm
I changed Apache::Session::DBI to Apache::Session::MySQL and tried
again.
What's the version number of your Apache::Session? It should be 1.54.
42: tie %session, 'Apache::Session::DBI',
43: {DataSource = dbi:$db_driver:sessions:$db_address};
With Apache::Session::MySQL, the docs say you
On Wed, 21 Nov 2001 23:23:33 -
Jonathan M. Hollin [EMAIL PROTECTED] wrote:
42: tie %session, 'Apache::Session::DBI',
43: {DataSource = dbi:$db_driver:sessions:$db_address};
put $sid (session id: undef for fresh) after 'Apache::Session::MySQL'.
--
Tatsuhiko Miyagawa [EMAIL PROTECTED]
Hi,
sorry, this is not exactly a mod_perl question but I hope somehow in the
wake of this issue.
Apache::Session::Store::Postgres problem:
After the initial login to my page, I define and tie a %session which
produces a _session_id that is totally different from what it stores in the
sessions
Hi,
I'm using the
precompiled binaries of Apache 1.3.20 + mod_perl on WinNT.
I have grabbed
Apache::Session 1.54 and nmake test fails at 99dbfile.t.
The test routine
basically hangs, and the culprit is in one of the last
lines:
tied(%$s)-delete;
It seems to be some
kind of file locking
which subclasses Apache::Session and contains all the
eXtentsion I need (most of them for Embperl, but they are also usefull
outside of Embperl). This also contains a replacement for
Apache::Session::Flex which can be configured via Makefile.PL and make test
is testing if this really works
is, that I have created a package named
Apache::SessionX which subclasses Apache::Session and contains all the
eXtentsion I need (most of them for Embperl, but they are also usefull
outside of Embperl). This also contains a replacement for
Apache::Session::Flex which can be configured via Makefile.PL
big
plans for it but I can at least integrate patches and such.
Apache::Session is in use in a lot of places and it would be good to have
an active maintainer.
++1. And I don't mind taking over, if nobody else wants to.
--
Tatsuhiko Miyagawa [EMAIL PROTECTED]
Apache::Session 1.54, also know as the you impatient bastards release,
has been uploaded to CPAN. Changes in this release include:
Fix ID validation in Flex
Move from MD5 to Digest::MD5
Include new generators ModUniqueId and ModUsertrack
-jwb
On Thu, 11 Oct 2001, Jeffrey W. Baker wrote:
Well, you guys are touchy lot! My releases are no less frequent than
releases of DBI or even mod_perl. So just chill out, I sometimes have
other things on my mind.
I don't know about touchy so much as frustrated. Apache::Session is very
widely
as frustrated. Apache::Session is very
widely used but it doesn't feel well supported.
Comparing it to DBI or mod_perl seems a bit silly. It is not as widely
used as either and is far less complex.
My big concern is that there is a fatal error in Apache::Session::Flex
that makes
Here is Apache::Session::Generate::* variants, which especially
uses Apache standard C-modules.
Apache::Session::Generate::ModUniqueId
http://bulknews.net/lib/archives/Apache-Session-Generate-ModUniqueId-0.01.tar.gz
http://bulknews.net/lib/archives/Apache-Session-Generate-ModUniqueId-0.01
Here is Apache::Session::Generate::* variants, which especially
uses Apache standard C-modules.
Apache::Session::Generate::ModUniqueId
http://bulknews.net/lib/archives/Apache-Session-Generate-ModUniqueId-0.01.ta
r.gz
http://bulknews.net/lib/archives/Apache-Session-Generate-ModUniqueId-0.01
These are now on CPAN, which I've forgotten to mention.
Note that if you try to use these modules functionality,
Apache::Session::Flex should be patched with one included in both
tarballs.
Thanks.
On Thu, 11 Oct 2001 01:30:29 +0900
Tatsuhiko Miyagawa [EMAIL PROTECTED] wrote:
Here
On Thu, 11 Oct 2001, Tatsuhiko Miyagawa wrote:
Note that if you try to use these modules functionality,
Apache::Session::Flex should be patched with one included in both
tarballs.
I sent a patch to Jeffrey last week or such that (I imagine) covers
the same thing.
--
ask bjoern hansen, http
On Thu, 11 Oct 2001, Tatsuhiko Miyagawa wrote:
Here is Apache::Session::Generate::* variants, which especially
uses Apache standard C-modules.
Apache::Session::Generate::ModUniqueId
http://bulknews.net/lib/archives/Apache-Session-Generate-ModUniqueId-0.01.tar.gz
http://bulknews.net/lib
101 - 200 of 484 matches
Mail list logo
