Announcing the Adapter module which provides a way to use
Cache::Cache subclasses as Apache::Session storage implementation.
http://bulknews.net/lib/archives/Apache-Session-CacheAny-0.01.readme
http://bulknews.net/lib/archives/Apache-Session-CacheAny-0.01.tar.gz
Any suggestions are welcome.
Tatsuhiko Miyagawa wrote:
Announcing the Adapter module which provides a way to use
Cache::Cache subclasses as Apache::Session storage implementation.
Hmmm...
Don't take this the wrong way, but what's the purpose of this?
Apache::Session does very little beyond what Cache::Cache does. In
Perrin Harkins writes:
Tatsuhiko Miyagawa wrote:
Announcing the Adapter module which provides a way to use
Cache::Cache subclasses as Apache::Session storage implementation.
Hmmm...
Apache::Session does very little beyond what Cache::Cache does. In
fact, the only things I
princepawn wrote:
Above and beyond the efficiency issues you discuss above, could you
comment on what Apache::Session would need to be useful in a serious
project?
I was commenting specifically on the ID generation. The algorithm
supplied does not guarantee unique IDs, especially when you
On Sun, 09 Sep 2001 15:24:14 -0700
Perrin Harkins [EMAIL PROTECTED] wrote:
Announcing the Adapter module which provides a way to use
Cache::Cache subclasses as Apache::Session storage implementation.
Hmmm...
Don't take this the wrong way, but what's the purpose of this?
To glue
Tatsuhiko Miyagawa wrote:
Cache::Cache is a cache interface for any key-value pairs with
optioinal automatic expire purge.
Apache::Session is a framework for persisntent hash data with
unique identifier and automatic serialiization/deserialization for
hash.
To me, they both look like
On Sun, 09 Sep 2001 18:33:11 -0700
Perrin Harkins [EMAIL PROTECTED] wrote:
To me, they both look like persistent hashes. Apache::Session assumes
you will be storing a serialized hash in each hash value, and that it
will generate IDs for keys if you don't supply one, but otherwise
they're
