On Sat, 7 May 2005, Stas Bekman wrote:
> Based on the input I had it looks that many people rely on
> registry doing chdir to the script's location. We don't do
> that in the current registry generation since this is not
> working under the threaded env and we want things to be
> working the same
On Sat, 7 May 2005, Stas Bekman wrote:
> As RC6 release didn't reveal any significant problems (a
> few minor bugs that are either already fixed or will be
> shortly), I propose that it's time to get 2.0.0 out. I was
> thinking to work next week to polish things and improve
> docs and get 2.0.0 to
As RC6 release didn't reveal any significant problems (a few minor bugs
that are either already fixed or will be shortly), I propose that it's
time to get 2.0.0 out. I was thinking to work next week to polish things
and improve docs and get 2.0.0 towards the end of the week/or the
beginning of
Based on the input I had it looks that many people rely on registry doing
chdir to the script's location. We don't do that in the current registry
generation since this is not working under the threaded env and we want
things to be working the same everywhere. There was a hope that Arthur
Bergm
Randy Kobes wrote:
On Sat, 7 May 2005, Stas Bekman wrote:
Randy Kobes wrote:
In the t/protocol/ tests, there's some comparisions of $@ to
APR::Const::ECONNABORTED and APR::Const::EOF made. As such,
it may be an idea to add and use
APR::Status::is_ECONNABORTED and APR::Status::is_EOF
instead. At th
Stas Bekman wrote:
[...]
This workaround doesn't sound right. A protocol handler (server) must be
able to start the conversation first. If not, many protocols relying on
the server's greeing (e.g. SMTP) won't work. e.g., see:
http://www.samlogic.net/articles/smtp.htm
I know that it would break som
On Sat, 7 May 2005, Stas Bekman wrote:
> Randy Kobes wrote:
> > In the t/protocol/ tests, there's some comparisions of $@ to
> > APR::Const::ECONNABORTED and APR::Const::EOF made. As such,
> > it may be an idea to add and use
> > APR::Status::is_ECONNABORTED and APR::Status::is_EOF
> > instead. At
Torsten Foertsch wrote:
On Saturday 07 May 2005 08:30, Stas Bekman wrote:
Torsten Foertsch wrote:
Hi,
yesterday I have patched my apache with this patch and now I have noticed
that testing mod_perl hangs in t/protocol/pseudo_http. The reason is
simple and to be expected. t/protocol/pseudo_http test
Randy Kobes wrote:
In the t/protocol/ tests, there's some comparisions of $@ to
APR::Const::ECONNABORTED and APR::Const::EOF made. As such,
it may be an idea to add and use
APR::Status::is_ECONNABORTED and APR::Status::is_EOF
instead. At the present time APR_EOF doesn't have any
variants:
#define
On Saturday 07 May 2005 08:30, Stas Bekman wrote:
> Torsten Foertsch wrote:
> > Hi,
> >
> > yesterday I have patched my apache with this patch and now I have noticed
> > that testing mod_perl hangs in t/protocol/pseudo_http. The reason is
> > simple and to be expected. t/protocol/pseudo_http tests
In the t/protocol/ tests, there's some comparisions of $@ to
APR::Const::ECONNABORTED and APR::Const::EOF made. As such,
it may be an idea to add and use
APR::Status::is_ECONNABORTED and APR::Status::is_EOF
instead. At the present time APR_EOF doesn't have any
variants:
#define APR_STATUS_IS_EOF(
11 matches
Mail list logo
