hi all
just following up on a thread in new-httpd from the weekend :)
in mp1, whenever a user set the filename via $r->filename($newfile) mod_perl
would update r->finfo as well. the reason is because things like
default_handler do this
ap_update_mtime(r, r->finfo.mtime);
...
a
Geoffrey Young wrote:
hi all
just following up on a thread in new-httpd from the weekend :)
in mp1, whenever a user set the filename via $r->filename($newfile)
mod_perl would update r->finfo as well. the reason is because things
like default_handler do this
ap_update_mtime(r, r->finfo
+1, but won't be better for Apache provide an API to set r->filename
which will take care of updating finfo?
yes, but you saw how quickly the thread died out when that idea was
introduced...
If Apache doesn't provide this
API, and wants users to do that when they really want to (as it involves
Geoffrey Young wrote:
+1, but won't be better for Apache provide an API to set r->filename
which will take care of updating finfo?
yes, but you saw how quickly the thread died out when that idea was
introduced...
like most other threads on httdp-dev list, which were lucky at all to become a
t
Stas Bekman wrote:
Geoffrey Young wrote:
+1, but won't be better for Apache provide an API to set r->filename
which will take care of updating finfo?
yes, but you saw how quickly the thread died out when that idea was
introduced...
like most other threads on httdp-dev list, which were luc
Geoffrey Young wrote:
Philippe has worked on it and he said that it won't work. See:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=104495193904477&w=2
I don't know if anything has changed since then.
right I remember that (though I thought there was some discussion on it
too).
anyway, I
anyway, I can't bring myself to belive that we can map the request_rec
to a class but we can't map apr_finfo_t. maybe it's my naivete
speaking, though :)
I believe you are trying to compare beer with cranberry juice.
request_rec is not used by perl, whereas perl wants finfo as returned by
s
Geoffrey Young wrote:
anyway, I can't bring myself to belive that we can map the
request_rec to a class but we can't map apr_finfo_t. maybe it's my
naivete speaking, though :)
I believe you are trying to compare beer with cranberry juice.
request_rec is not used by perl, whereas perl wants f
Steve Hay wrote:
At least I have found a sure way to verify that a segfault is caused by the
wrong context. When you get a core trace where a Perl_ call, passing
interpreter argument (my_perl on Unix, interpreter on win32), is followed by
another Perl_ call, which doesn't pass this argument, go
