On Sat, Apr 13, 2002 at 04:33:11PM +0200, Eric Cholet wrote:
I'm seeing this problem when using Apache::SOAP, using Cache::Cache
0.99 or 1.0. Downgrading to Digest::MD5 2.12 indeed solves it.
Hi -- I recently released version 1.01 of Cache::Cache to CPAN. This
version uses Digest::SHA1 as a
-cache/
The following is the Cache-Cache-1.0 README file:
Copyright (C) 2001 DeWitt Clinton All Rights Reserved
You may distribute under the terms of either the GNU General Public
License or the Artistic License, as specified in the Perl README file.
NAME
Cache::Cache
DESCRIPTION
On Sun, Apr 07, 2002 at 08:52:59PM +0300, Issac Goldstand wrote:
So how exactly is the auto_purge meant to be used - the
documentation is very hazy on that point (sure I can patch it - but
you have to explain it to me first :)), and I just got lost when
looknig at the module source.
The
On Sat, Dec 22, 2001 at 06:11:33AM -0800, brian moseley wrote:
doesn't it seem like there should be a way to denote object
data as transient so that it doesn't get serialized by
Storable, etc?
I'd love that as well. For example, when persisting Cache::Object
instances I manually strip out
On Sat, Dec 22, 2001 at 10:39:03PM +0900, Tatsuhiko Miyagawa wrote:
One instance for one server (across all httpd processes).
Implemented using Cache::SharedMemoryCache (IPC).
Maybe you want to consider directly using Cache::SharedMemoryBackend
instead of the SharedMemoryCache class. The
On Wed, Dec 12, 2001 at 03:05:33PM +1100, Rob Mueller (fastmail) wrote:
I sat down the other day and wrote a test script to try out various
caching implementations. The script is pretty basic at the moment, I
just wanted to get an idea of the performance of different methods.
Rob, wow! This
On Tue, Dec 11, 2001 at 02:31:36AM -0800, Paul Lindner wrote:
Right. A more elaborate Apache::CacheContent would have a filename
hash function, and a separate cache directory structure along the
lines of Cache::FileCache.
Just curious -- any reason not to use Cache::Cache as the persistance
tree (viewcvs):
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/perl-cache/
The following is the Cache-Cache-0.99 README file:
Copyright (C) 2001 DeWitt Clinton All Rights Reserved
You may distribute under the terms of either the GNU General Public
License or the Artistic License
On Mon, Nov 19, 2001 at 07:51:55AM -0800, Randal L. Schwartz wrote:
But this is obvious. I'm confused about why I'd have to explain it. :(
I posted this a year or two back:
[EMAIL PROTECTED]">http://mathforum.org/epigone/modperl/jytwortwor/[EMAIL PROTECTED]
Here is the relevant part of
On Thu, Nov 08, 2001 at 01:11:21PM -0500, Barrie Slaymaker wrote:
Even a bit more OT: one thing to watch out for, especially if you
plan on caching a *lot* of data, is that the Cache::* modules did
not do collision detection on MD5 collisions the last time I looked.
Forgive me if that's
On Wed, Oct 03, 2001 at 04:43:41PM -0700, Jeffrey W. Baker wrote:
I'd also like to hear people's opinions on XML::DOM (I think it
stinks and I've replaced it with a C DOM implementation).
You just proved that you already know everything you need to on the
subject of XML::DOM. :)
Seriously
On Fri, Sep 28, 2001 at 08:49:22AM -0700, Nick Tonkin wrote:
Cache::FileCache defaults to using /tmp for the location of its
cache; does the system have /tmp (not sure what Cache::FileCache does if
there's no /tmp, hafta look at the code).
You can manually override the temp directory by
://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/perl-cache/
The following is the Cache-Cache-0.09 README file:
Copyright (C) 2001 DeWitt Clinton All Rights Reserved
You may distribute under the terms of either the GNU General Public
License or the Artistic License, as specified in the Perl README
Hi,
If people have a moment, please check out Cache::Cache 0.09, which is
available here until I am ready to release it on CPAN:
http://prdownloads.sourceforge.net/perl-cache/Cache-Cache-0.09.tar.gz
Changes include:
- applied Axel Beckert patch to fix the expiration units
- applied
On Tue, Sep 04, 2001 at 12:14:52PM -0700, Rob Bloodgood wrote:
***OH WOW!*** So, DURING the course of composing this message, I've
realized that the function expire_old_accounts() is now redundant!
Cache::Cache takes care of that, both with expires_in and max_size. I'm
leaving it in for
On Tue, Aug 07, 2001 at 08:18:18PM +1000, Cees Hek wrote:
So what your saying is that you have a list of potentially rooted machines
that you are making publically available... Doesn't sound like such a
good idea to me...
So *that's* why Reuven has CodeRed.pm CC him on the warning emails.
On Sat, Aug 04, 2001 at 09:17:21AM -0700, brian moseley wrote:
could this be because i'm only ever doing one set, at
session creation time? since i'm using a memory cache, i
didn't expect to have to call set every time i modify the
cached data.
Yup. That would be it. Please see my
On Sat, Aug 04, 2001 at 10:34:34AM -0700, brian moseley wrote:
ps: i've modified my code to 1) only get once per request
and 2) set at the end of each request. the net effect is
that stuff works as expected. i'm reasonably happy with the
current state of affairs, but...
Excellent, this is
On Sat, Aug 04, 2001 at 03:06:37PM -0400, DeWitt Clinton wrote:
To quote Jimi Williams, manager's decision.
Yes, I know it is Jimy Williams. See what happens when a lifelong Red
Sox fan relocates down to NYC? We start losing our minds... :)
-DeWitt
-cache/
The following is the Cache-Cache-0.08 README file:
Copyright (C) 2001 DeWitt Clinton All Rights Reserved
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation
On Tue, Mar 27, 2001 at 09:50:33PM +0100, Matt wrote:
I want to cache some values in my handlers so they don't keep having
to look stuff up, and so I figured a Cache::SharedMemoryCache would
be the way to go.
It all depends on what you want to cache and why. If you wanted to
save a trip to
On Tue, Mar 27, 2001 at 05:19:15PM -0500, Pierre Phaneuf wrote:
DeWitt Clinton wrote:
The other question is whether or not to share the cache instance
itself globally. Technically, this is up to you. Personally I
wouldn't bother, considering the overhead of instantiating the
cache
is the Cache-Cache-0.05 README file:
Copyright (C) 2001 DeWitt Clinton All Rights Reserved
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 1
://cvs.sourceforge.net/cgi-bin/cvsweb.cgi?cvsroot=perl-cache
The following is the Cache-Cache-0.04 README file:
Copyright (C) 2001 DeWitt Clinton All Rights Reserved
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License
On Sun, Mar 11, 2001 at 03:33:12PM +0100, Christian Jaeger wrote:
I've looked at Cache::FileCache now and think it's (currently) not
possible to use for IPC::FsSharevars:
I really miss locking capabilities. Imagine a script that reads a
value at the beginning of a request and writes it
.sourceforge.net/perl-cache/Cache-Cache-0.03.tar.gz
Changelog:
http://sourceforge.net/project/shownotes.php?release_id=26779
CVS tree (cvsweb):
http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi?cvsroot=perl-cache
The following is the Cache-Cache-0.03 README file:
Copyright (C) 2001 DeWitt Clinton
On Sat, Mar 10, 2001 at 11:17:21AM -0800, Bill Moseley wrote:
When you say successor to File::Cache does that means File::Cache
will not be maintained as a separate module anymore?
There are no features in File::Cache that will not exist in
Cache::FileCache and Cache::SizeAwareFileCache.
On Sat, Mar 10, 2001 at 02:00:34PM -0600, Daniel Little (Metrex) wrote:
Along the same lines, how about making SizeAwareMemoryCache as well
so that you can specify just how much data you want stored in the
cache.
Good idea. I'll add that to the 0.04 feature list as well.
Thanks!
-DeWitt
On Sat, Mar 10, 2001 at 12:10:35PM -0800, Perrin Harkins wrote:
"Daniel Little (Metrex)" wrote:
Along the same lines, how about making SizeAwareMemoryCache as well so that
you can specify just how much data you want stored in the cache.
Sounds like Joshua Chamas' Tie::Cache module. It
On Sat, Mar 10, 2001 at 04:35:02PM -0800, Perrin Harkins wrote:
Christian Jaeger wrote:
Yes, it uses a separate file for each variable. This way also locking
is solved, each variable has it's own file lock.
You should take a look at DeWitt Clinton's Cache::FileCache module,
announced on
Summary:
Perl Cache is the successor to the popular File::Cache and
IPC::Cache perl libraries. This project unifies those modules under
the generic Cache::Cache interface and implements Cache::FileCache,
Cache::MemoryCache, Cache::SharedMemoryCache, and
Cache::SizeAwareFileCache.
On Fri, Feb 16, 2001 at 03:14:37PM +, Matt Sergeant wrote:
I wonder if I should write them an article about take23, and then
use the funds to pay for articles for take23 :-)
Geez, Matt, you promote take23 every chance you get.
That's worse than me mentioning Avacet
Hello:
Perl Cache is the successor to the popular File::Cache and
IPC::Cache perl libraries. This project unifies those modules under
the generic Cache::Cache interface and implements Cache::FileCache,
Cache::MemoryCache, and Cache::SharedMemoryCache.
The project is being hosted on
On Wed, Feb 07, 2001 at 04:02:39PM +0400, BeerBong wrote:
Cache size after 24 hours of working
via 'du -s' - 53M
via 'perl -MFile::Cacje -e"print File::Cache::SIZE('PRTL')"' - 10M
That looks like a serious bug. Can you double check on that? Where
are you running the "du -s"?
The SIZE( )
On Tue, Jan 23, 2001 at 10:06:13AM +, Matt Sergeant wrote:
The only gain might be in a large DOM tree where there may be
thousands of objects. But then you're really better off using an
array based class instead (as I found out).
This is getting a bit off-topic, but I'm empirically found
On Mon, Jan 08, 2001 at 10:10:25AM -0800, Perrin Harkins wrote:
Always start with CPAN. Try Tie::FileLRUCache or File::Cache for
starters. A dbm would be fine too, but more trouble to purge old
entries from.
If you find that File::Cache works for you, then you may also want to
check out the
Hi! I've been quiet for a while on this list, but I still read it
religiously. I wanted to take a second and share our announcement of
the release of the second beta of the Avacet Application Engine.
Version 2.0b2 of the Avacet Application Engine is available for
download at
ck, advice, and criticism are
always welcome.
-DeWitt
README:
Copyright (C) 2000 DeWitt Clinton [EMAIL PROTECTED], Avacet, Inc.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software
On Wed, May 31, 2000 at 04:16:09PM -0700, Perrin Harkins wrote:
Maybe I'm just being thick, but if you leave out the event driven parts of
the spec, what's left that isn't just an ordinary Perl class? You can
easily make classes to hold data using Class::Struct or
Class::MethodMaker.
In
Hi all,
Okay, this is a rather ridiculous question. I spent the weekend
implementing a property based object model in Java. However, after I
finished, someone in my company laughingly pointed out that I had just
re-invented Java beans. While there were some minor advantages to the
model I
On Mon, May 22, 2000 at 12:06:20PM -0700, Karyn Ulriksen wrote:
IPC::Cache has worked like a champ for me on a heavily loaded webserver.
It's simple and (I'm lead to believe) it's a compiled module. You interact
with it like a hash file, but if you're clever you can work it out for your
On Mon, May 22, 2000 at 04:35:54PM -0400, Drew Taylor wrote:
Could I ask what the problems you were having? I can't use
IPC::SharedCache currently because I get the error "Couldn't find free
segment" or something like that when trying to initialize the cache. The
system engineers are
On Mon, May 22, 2000 at 03:46:41PM -0700, Karyn Ulriksen wrote:
I know what beta testing is, so I hope you didn't think I was trying to yank
your chain! I knew that if it got ugly I could easily take that server
offline and easily back out the code.
Ack! I'm sorry for what I think is a
Hi,
Interesting thread and interesting question.
It makes sense to start with the requirements for what it means to
implement those secure features. My requirements have an obvious
e-commerce bias, and should probably be heavily reviewed by anyone
thinking of using this design for
On Thu, 3 Feb 2000, Peter Skipworth wrote:
Does anyone have any experience in using IPC shared memory or similar in
caching data amongst multiple httpd daemons ?
Well, I just released IPC::Cache version 0.02 to CPAN. Two major caveats,
however -- first, it is not currently in production on
Hi,
[I sent this out a while back, but it never made it through. Odd.]
Based on some great feedback from this list, I was able to remove the
dependency on IPC::Shareable. Not that I dislike IPC::Shareable -- to the
contrary, it does what it does rather well -- but I was really looking for
Hi,
A week or two ago, in the squid performance thread, I mentioned that I was
looking for ways to eliminate squid from our production servers. I noted
that we are using squid to save an expensive trip to the database to
retrieve mostly static files. At that time I said that I planned to write
[apologies if people get this twice -- it seemed to bounce the first time]
We've been getting many segv's and bus errors on apache processes since
adding modperl. Env: Apache 1.3.11 (though we had the same thing
under 1.3.9.), Perl 5.005003, modperl 1.21, hpux 11.00.
If you compare this to
On Fri, 14 Jan 2000 [EMAIL PROTECTED] wrote:
Hi, I am switching my modperl site to squid in httpd acclerator mode
and everything works as advertised, but was very surprised to find
squid 10x slower than apache on a cached 6k gif as measured by
apache bench... 100 requests/second vs almost
On Sun, 16 Jan 2000, Steven Lembark wrote:
given you have the core to support it... try using libmm and
a tied hash to just stash the stuff until it's asked for.
Actually, we are currently developing a generic object caching interface
that will support a TTL based on expiration dates, and
On Thu, 9 Dec 1999, Gerald Richter wrote:
The problem is, that Embperl must know, that you want to run in a Safe
compartement. Just add
'options' = HTML::Embperl::optSafeNamespace
to the Excute parameters and it should work.
Right. That makes sense, and it is definitely a good idea to
On Thu, 9 Dec 1999, Gerald Richter wrote:
Rereading your first mail, seems to me that there is an additional problem
with Embperl's cleanup. This has nothing todo with Safe namespaces. Embperl
will per default tidyup your namespace and therefor execute something like
$vars = undef at the end
On Thu, 9 Dec 1999, Gerald Richter wrote:
If I had understand you right, the first call via execute to your template
works and the second not, right?
That's not a bug! Embperl cleans up all your global variables inside your
page after every request. $vars in your template is such a global
On Thu, 9 Dec 1999, Gerald Richter wrote:
So the solution to your problem should be, to use a fixed package name for
all calls to the _same_ page.
Brilliant! This does address exactly the problem I raised, and makes
perfect sense.
I had to do one absolutely wacky thing, though. Because I
54 matches
Mail list logo
