Stas Bekman wrote:
Geoffrey Young wrote:
I would want at least a real-time interface for this, something
similar to
$filter->init(sub {shift->update_mtime($package_mtime)} );
where would you run this code?
outsite of a handler() subroutine, pretty much like I showed it - on
module
Geoffrey Young wrote:
I would want at least a real-time interface for this, something
similar to
$filter->init(sub {shift->update_mtime($package_mtime)} );
where would you run this code?
outsite of a handler() subroutine, pretty much like I showed it - on
module load. I suspect you'd h
I would want at least a real-time interface for this, something
similar to
$filter->init(sub {shift->update_mtime($package_mtime)} );
where would you run this code?
outsite of a handler() subroutine, pretty much like I showed it - on
module load. I suspect you'd have to register the init
Geoffrey Young wrote:
[...]
no, you need the real filter_init hook.
the issue here is that default_handler has meets_condiditions() logic in
it, so it makes decisions about whether or not to send content down the
chain. this is generally bad for filters, since they may have their own
criteria
Dmitri Tikhonov wrote:
On Fri, 17 Jan 2003, Stas Bekman wrote:
Dmitri Tikhonov wrote:
I upgraded to 1.99.08 a couple of days ago and noticed strange behavior
in my CGI scripts that run under ModPerl::Registry -- in 1.99.07 they
worked fine. In 1.99.08, however, every single one of my scrip
Stas Bekman wrote:
Geoffrey Young wrote:
Finally, other than add/remove filters APIs which we have talked
about, what other APIs do you want for filters?
is there an interface to filter_init?
see the discussion on
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9673
or CHANGES file
