Dossy Shiobara said:
I disagree: I think whether to persist the cache to disk should be
specified when the cache is created, not when an cache entry is
That's really what I meant.
output in a file named $cachedir/$adppath/$xx/[md5 $adpargs].dat, where
$xx might be the first 2 characters of
On 2005.06.28, Bas Scheffers [EMAIL PROTECTED] wrote:
I have never use ns_cache before, but it seems to me there is no way to
store something in the cache from Tcl, is that the case? Would it be
possible to implement?
See the stand-alone nscache module. I have NO idea why this isn't part
of
Dossy Shiobara said:
Not crazy at all. I think of nscache as a specialized NSV that has an
upper bound to either size or age.
That's what I think of it, the inital though was using NSVs, but that
would require manual cleanup, hence using cache for it instead.
I'll have a look at the nscache
On Tue, Jun 28, 2005 at 11:01:14AM -0400, Dossy Shiobara wrote:
See the stand-alone nscache module. I have NO idea why this isn't part
of the AOLserver core ... unless folks really object, I think we should
fold the nscache module in.
All nscache is really doing is providing some Tcl APIs to
On Jun 28, 2005, at 11:01 AM, Dossy Shiobara wrote:
On 2005.06.28, Bas Scheffers [EMAIL PROTECTED] wrote:
I have never use ns_cache before, but it seems to me there is no
way to
store something in the cache from Tcl, is that the case? Would it be
possible to implement?
See the stand-alone
On Tuesday 28 June 2005 08:13, Bas Scheffers wrote:
I'll have a look at the nscache module and see what I can do on creating
sessions in Tcl this week. I am not a heavy user of them, but some light
information like user_id and name and such will save me a roundtrip to the
DB on every page.
On Tue, Jun 28, 2005 at 10:42:33AM -0700, Tom Jackson wrote:
On Tuesday 28 June 2005 08:13, Bas Scheffers wrote:
I'll have a look at the nscache module and see what I can do on creating
sessions in Tcl this week. I am not a heavy user of them, but some light
information like user_id and
On Tuesday 28 June 2005 11:47, Andrew Piskorski wrote:
On Tue, Jun 28, 2005 at 10:42:33AM -0700, Tom Jackson wrote:
Here are some ideas using a file based storage:
If you're already using an RDBMS anyway, why would you want to store
session info in files rather than the RDBMS? And if you
This sounds very interesting! Few questions about the cache:
Where does it store the generated pages? Just in memory, or on disk?
What is used as key for the cached page, the arguments you pass the ADP?
How do you clear the cache?
Cheers,
Bas.
Jim Davidson said:
Yup -- agreed, default has to
On 2005.06.27, Bas Scheffers [EMAIL PROTECTED] wrote:
This sounds very interesting! Few questions about the cache:
Where does it store the generated pages? Just in memory, or on disk?
In an Ns_Cache named nsadp:$servername:$itPtr, it looks like -- I'm not
sure why it's in a per-interp cache,
Hi,
The cache is actually a bit complex to follow -- I'll add some
comments to help describe. Basically:
-- Each thread maintains a cache of ADP code which includes per-
interp byte codes and pointers to text regions in a shared area.
When all threads no longer point to the shared text, it's
Dossy Shiobara said:
This really ought to be a server-wide cache sitting in
servPtr-adp.cache rather than itPtr-adp.cache ...
I would think so! :) The problem with that still is that it is not
persistent, which could mean that if you restart your server under high
load, all the cache generation
On 2005.06.27, Bas Scheffers [EMAIL PROTECTED] wrote:
Dossy Shiobara said:
This really ought to be a server-wide cache sitting in
servPtr-adp.cache rather than itPtr-adp.cache ...
I would think so! :) The problem with that still is that it is not
persistent, which could mean that if you
Yup -- agreed, default has to be no-caching to be backwards
compatible. I think that's how the code works -- at least that was
my goal but I could have screwed it up :) I'll take a look.
-Jim
On Jun 25, 2005, at 10:20 PM, Dossy Shiobara wrote:
On 2005.06.25, Jim Davidson [EMAIL
If I understand correctly, AOLServer 4.1 is currently under
development. What features, fixes will be delivered for that release?
And, when is the proposed delivery date? Is there a location which
contains the above information?
Thank you
--
Ramesh
--
AOLserver - http://www.aolserver.com/
To
Hi,
We should put a page on aolserver.com with some details. We've moved
the version to 4.5 from 4.1 to reflect the scope of changes.
Scanning the ChangeLog and from what I can recall:
* New connection management features including the ns_limits and
ns_pools commands:
-- ns_limits: control #
On Jun 25, 2005, at 2:27 PM, Jim Davidson wrote:
Hi,
We should put a page on aolserver.com with some details. We've moved
the version to 4.5 from 4.1 to reflect the scope of changes.
Scanning the ChangeLog and from what I can recall:
Thanks for the comprehensive information. I agree with you
On 2005.06.25, Jim Davidson [EMAIL PROTECTED] wrote:
* ADP improvements including:
-- A new execution caching technique at the ns_adp_include level [...]
Embedded ns_adp_include's with the -nocache flag at lower levels allow
you to still execute dynamic code within cached blocks if necessary.
18 matches
Mail list logo
