+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
Howdy all, is a module written under v2.0.54 supposed to be
able to work with apache 2.2 without being recompiled ?
Apologies if this is a rtfm question.
--markc
On Sun, 17 Sep 2006, Graham Leggett wrote:
Niklas Edmundsson wrote:
However, I don't see how you can do a lockless design with multiple files
and an index that can do:
* Clients read from the cache as files are being cached.
* Only one session caches the same file.
* Header/Body updates.
*
Howdy all, is a module written under v2.0.54 supposed to be
able to work with apache 2.2 without being recompiled ?
Mark,
It is my understanding that binary compatibility is only assured within minor
releases (i.e. 2.0.30 to 2.0.46). The jump from 2.0 to 2.2 is a major release
jump and would
On Mon, September 18, 2006 9:35 am, Niklas Edmundsson wrote:
The easiest way to deal with this might be to have a timeout, if the
body hasn't shown up in $timeout time then something went bad,
DECLINE, meaning that the cache layer thinks it should cache the file
and acts accordingly. You
Niklas Edmundsson wrote:
Extra tracking sounds unnecessary if you can do it in a way that
doesn't need it.
It's not extra it just adding some tracking. When an objects gets
cached log (sql, db, whatever) that /blah/foo/bar.html is cached as
/cache/x/y/something.meta. Then it's very easy
Graham Leggett wrote:
I have not seen inside the htcacheclean code, why is the code reading the
headers? In theory the cache should be purged based on last access time,
deleted as space is needed.
Everyone should be mounting cache directories noatime, unless they don't
care about
Brian Akins wrote:
Niklas Edmundsson wrote:
Extra tracking sounds unnecessary if you can do it in a way that
doesn't need it.
It's not extra it just adding some tracking. When an objects gets
cached log (sql, db, whatever) that /blah/foo/bar.html is cached as
Issac Goldstand wrote:
I can see how other tracking information (like how often the
cached entity is accessed, last access time, etc) would be useful,
Also, those statistics could be updated asynchronously by using a queue
so that statistics doesn't slow down a busy web server.
--
Brian
Brian Akins wrote:
Issac Goldstand wrote:
I can see how other tracking information (like how often the
cached entity is accessed, last access time, etc) would be useful,
albeit expensive to keep track of, but I don't understand this specific
example.
It's not expensive, as these
Brian Akins wrote:
Issac Goldstand wrote:
I can see how other tracking information (like how often the
cached entity is accessed, last access time, etc) would be useful,
Also, those statistics could be updated asynchronously by using a queue
so that statistics doesn't slow down a busy
Am Donnerstag, den 01.06.2006, 16:36 +0200 schrieb Plüm, Rüdiger, VF
EITO:
As far as I remember there had been also a discussion on who owns a brigade.
So who has to call / should not call apr_brigade_destroy / apr_brigade_cleanup
in the filter chain. I think rules for this would be also
Helmut Tessarek [EMAIL PROTECTED] writes:
Hi,
Howdy all, is a module written under v2.0.54 supposed to be
able to work with apache 2.2 without being recompiled ?
I even had to change the code of my module a little bit.
I had a really hard time finding with specific documentation. So far
14 matches
Mail list logo
