I like Quetzalcoatl and PyPache. Terrarium seemed nice at first, but then
the ophidiophobia in me took over. (Nobody suggested ophis, btw..)
On Wed, 16 May 2007, Gregory (Grisha) Trubetskoy wrote:
So I think we've got (in no particular order):
PythonScript
Pythonidae
PyPache
pythonalia
Gregory (Grisha) Trubetskoy wrote:
I like Quetzalcoatl and PyPache.
Quetzalcoatl is still my sentimental favourite.
Perhaps I'm overly concerned with potential search problems for
Quetzalcoatl, considering that Google is pretty good at figuring out
spelling errors. Also the mod_python
In mod_python 3.2.x, if I set a directory to use mod_python with a
.htaccess file, I will find that directory in sys.path. That is, if:
/var/www/somedir/.htaccess
contains:
SetHandler python-program
then sys.path will have /var/www/somedir as element zero.
With 3.3.x this does not
In mod_python 3.2.x, if I set a directory to use mod_python with a
.htaccess file, I will find that directory in sys.path. That is, if:
/var/www/somedir/.htaccess
contains:
SetHandler python-program
then sys.path will have /var/www/somedir as element zero.
With 3.3.x this does not
+1 for PyPache
On Wed May 16 2007 02:06 pm Gregory (Grisha) Trubetskoy wrote:
So I think we've got (in no particular order):
PythonScript
Pythonidae
PyPache
pythonalia
Quetzalcoatl
Asphyxia
Scales
Pythonistas
PigeonPy
Pungi
Would people (ANYONE here on the list, yes, that includes
How about this last minute entry as a place to keep our snake?
Apache Terrarium
+1 on terrarium.apache.org
On 18/05/07, Gregory (Grisha) Trubetskoy [EMAIL PROTECTED] wrote:
On Thu, 17 May 2007, Jim Gallacher wrote:
Quetzalcoatl is still my sentimental favourite.
Perhaps I'm overly concerned with potential search problems for
Quetzalcoatl, considering that Google is pretty good at figuring out
Graham Dumpleton writes:
Read:
http://www.modpython.org/live/current/doc-html/pyapi-apmeth.html
Especially the area which starts just before:
PythonOption mod_python.importer.path ['~']
Your particular issue is mentioned just after this example.
Doesn't work, either in .htaccess
On 18/05/07, Daniel J. Popowich [EMAIL PROTECTED] wrote:
Graham Dumpleton writes:
Read:
http://www.modpython.org/live/current/doc-html/pyapi-apmeth.html
Especially the area which starts just before:
PythonOption mod_python.importer.path ['~']
Your particular issue is mentioned just
I worked it out. As my change didn't disable the mpservlets caching
system, it was never triggering the module importer again to perform
its own checks. Thus, if I add:
klass, cached_mtime, servlets = self.class_cache.get(fname,
In my work writing mod_wsgi where I do something similar to mod_cgid
and fork off multiple daemon child processes which do special stuff
rather than what the normal Apache child processes do, it occurred to
me that a generic module which could be configured to spawn off
processes, swap user
On 5/9/07, Jojy Varghese [EMAIL PROTECTED] wrote:
We are currently exploring different strategies for testing an HTTP
server for different scenarios around HTTP protocol compliance and load
conditions. I was wondering if apache has a test suite for testing its http
server. Any help is much
On 5/17/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
@@ -298,6 +298,8 @@
http://people.apache.org/~jerenkrantz/max-age-2.2.x.patch
(Trivially conflicts with CacheIgnoreQueryString above.)
+1: jerenkrantz
+ rpluem asks: Why not backporting the adjusted error message
Has there been any progress on PR41230? I submitted a patch that at
least seems to improve the situation that now seems to have seen some
testing by others as well.
As I have stated before, it would be really nice if a fix for this
could be committed, be it my patch or some other solution.
On 05/17/2007 08:25 PM, [EMAIL PROTECTED] wrote:
Author: jerenkrantz
Date: Thu May 17 11:25:13 2007
New Revision: 539063
Modified: httpd/httpd/trunk/modules/cache/mod_cache.c
URL:
On 5/17/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
+ rpluem : Now that CacheIgnoreQueryString has been backported r538807
+ applies cleanly to 2.2.x. So I assume it is ok to use
+ r538807 instead of max-age-2.2.x.patch.
Aye - that's fine and just
On 05/17/2007 10:56 PM, Justin Erenkrantz wrote:
On 5/17/07, Ruediger Pluem [EMAIL PROTECTED] wrote:
+x = apr_atoi64(max_age_val);
+if (errno) {
+x = conf-defex;
Hm. Shouldn't we adjust the bogus max-age field value in the
Cache-Control header
PyPache +1
Jeffrey Robbins a écrit :
Scales works for me - I like the double entendre
-Original Message-
From: Jorey Bump [EMAIL PROTECTED]
Date: Wednesday, May 16, 2007 5:51 pm
Subject: Re: TLP Name
To: Gregory (Grisha) Trubetskoy [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
For me, it's
On 05/17/2007 11:28 PM, Justin Erenkrantz wrote:
On 5/17/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
+ rpluem : Now that CacheIgnoreQueryString has been backported
r538807
+ applies cleanly to 2.2.x. So I assume it is ok to use
+ r538807
On 5/17/07, Ruediger Pluem [EMAIL PROTECTED] wrote:
But it already does in the case of the Expires header. If the Expires
header is missing or bogus and no max-age field is present (valid or invalid),
we set one with the expires date the cache calculated (either heuristic or
default). And this
On 5/17/07, Ruediger Pluem [EMAIL PROTECTED] wrote:
As Roy has already voted for it before I added my comment, I just wanted to give
him a chance to give a comment if he thinks that this is needed (in the same
way as
I wanted to give you a chance to comment). But in this simple case it may not
I'm processing some custom XML of considerable length in an output
filter and I collect the entire response, flatten it, process it, then
pass it on. One particular response body comprises 17 brigades of which 5
are zero length. As I'm coalescing these bucket brigades, is it correct
Read:
http://www.modpython.org/live/current/doc-html/pyapi-apmeth.html
Especially the area which starts just before:
PythonOption mod_python.importer.path ['~']
Your particular issue is mentioned just after this example.
Graham
On 18/05/07, Daniel J. Popowich [EMAIL PROTECTED] wrote:
In
On May 17, 2007, at 2:48 PM, Ruediger Pluem wrote:
On 05/17/2007 11:28 PM, Justin Erenkrantz wrote:
On 5/17/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
+ rpluem : Now that CacheIgnoreQueryString has been
backported
r538807
+ applies cleanly to 2.2.x. So I assume
On May 17, 2007, at 2:53 PM, Justin Erenkrantz wrote:
BTW, I'm not a fan of us inventing Expires headers in this section of
code - I'd think it'd be far cleaner to off-load Expires response
header generation to mod_expires and leave the cache out of it
entirely - inventing Expires values deep
On 5/17/07, Niklas Edmundsson [EMAIL PROTECTED] wrote:
Has there been any progress on PR41230? I submitted a patch that at
least seems to improve the situation that now seems to have seen some
testing by others as well.
As I have stated before, it would be really nice if a fix for this
could be
On 05/18/2007 12:19 AM, Roy T. Fielding wrote:
On May 17, 2007, at 2:53 PM, Justin Erenkrantz wrote:
BTW, I'm not a fan of us inventing Expires headers in this section of
I don't want to pick on you, but ironically it was you who introduced this :-)
On 5/17/07, Roy T. Fielding [EMAIL PROTECTED] wrote:
On May 17, 2007, at 2:53 PM, Justin Erenkrantz wrote:
BTW, I'm not a fan of us inventing Expires headers in this section of
code - I'd think it'd be far cleaner to off-load Expires response
header generation to mod_expires and leave the
On 5/17/07, Ruediger Pluem [EMAIL PROTECTED] wrote:
I don't want to pick on you, but ironically it was you who introduced this :-)
(http://svn.apache.org/viewvc?view=revrevision=152973).
Oh, it probably was. What can I say? I'm less stupid now. =)
Ok. So we should remove the
On May 17, 2007, at 4:37 PM, Justin Erenkrantz wrote:
See the patch I just posted - we should also remove the Date
manipulation too, IMO.
Probably. If Date is added, it should be done by the protocol filter
(mod_proxy) when the message is received, not the cache.
Just for clarification: It
On 05/18/2007 01:26 AM, Justin Erenkrantz wrote:
On 5/17/07, Niklas Edmundsson [EMAIL PROTECTED] wrote:
Has there been any progress on PR41230? I submitted a patch that at
least seems to improve the situation that now seems to have seen some
testing by others as well.
As I have stated
On 05/18/2007 01:33 AM, Justin Erenkrantz wrote:
With this patch, the only thing mod_cache ever touches is...Age. =)
I'll let this sit here for a bit and if we agree this is right, we can
commit. -- justin
Index: modules/cache/mod_cache.c
+1 on pypache
Had a couple hours while on vacation after reading PiL. This makes
connection, server, and apr_table into real lua modules. I also separated
out the code and started playing with getters and setters.
I like the idea of doing the function tables in plain C, rather than Lua
C. Mostly because I
On 5/17/07, Ruediger Pluem [EMAIL PROTECTED] wrote:
Hm. In this case date would be undefined and it is used later on.
Oh. Good catch.
Maybe we should remove the else branch and set date = info-date in
any case so that it is either the contents of Date: or now.
Sure. That'll work.
See
On 5/17/07, Ruediger Pluem [EMAIL PROTECTED] wrote:
why. Also the entity is not physically removed from the cache if it is really
stale.
This does not matter in the non HEAD case as it gets overwritten by the fresh
response,
but in the HEAD case it should be physically removed IMO.
Well,
On 5/17/07, Akins, Brian [EMAIL PROTECTED] wrote:
Had a couple hours while on vacation after reading PiL. This makes
connection, server, and apr_table into real lua modules. I also separated
out the code and started playing with getters and setters.
I like the idea of doing the function
[EMAIL PROTECTED] wrote:
http://people.apache.org/~wrowe/mpm_winnt_waits.patch
is easier to read (-U8)
+1: mturk
+ +0: fielding (patch is okay, underlying code is crap)
wrowe notes: a patch should have the necessary effect with the
minimum lines
38 matches
Mail list logo
