* Geoffrey Young [EMAIL PROTECTED] wrote:
If I'm using stacked handlers, what should I return if I
dont want the next handler in line to run because I've returned
all required content to the client? (the eagle book says
anything other than OK, DECLINED or DONE, but what's the
* Mark Maunder [EMAIL PROTECTED] wrote:
Nikolaus Rath wrote:
* Mark Maunder [EMAIL PROTECTED] wrote:
Hi,
If I'm using stacked handlers, what should I return if I dont want the
next handler in line to run because I've returned all required content
to the client? (the eagle book says
what is wrong with DONE? DONE immediatly closes the client
connection
and starts the logging phase. if you have sent the content already
then there is nothing to worry about. the call to send_http_header
will pick up on the any status you set previously or use the default
HTTP_OK
Geoffrey Young wrote:
what is wrong with DONE? DONE immediatly closes the client
connection
and starts the logging phase. if you have sent the content already
then there is nothing to worry about. the call to send_http_header
will pick up on the any status you set previously or
I need to make an upload meter for a project that
I'm working on, and was wondering if it was worth making a generic one and
puting it under the Apache::* namespace (probably Apache::UploadMeter).
The reason that I'm asking is because it's going to need a rather extensive
configuration to
Firstly, I am curious...
Why was Berkeley DB chosen for caching when a RDBMS (mysql in this case)
was already being used?
Secondly, I've worked on a good-sized commerce site with
mod_perl+HTML::Mason. One of the more dirty secrets is that the back-end
of the site involves several standalone
For comparions, a nice aspect of j2ee applications IMHO is the
application server tends to be more general. ie. the application
server is not just the web server (as it is with mod_perl). I've found
j2ee features such as message beans, queues and such especially useful
for back-end work.
on 10/22/01 11:13 AM, Matthew Kennedy at [EMAIL PROTECTED] wrote:
Why was Berkeley DB chosen for caching when a RDBMS (mysql in this case)
was already being used?
It's faster and less resource-intensive for this kind of thing. We just
wanted a really fast persistent hash, and didn't need SQL
I've released a new version of ApacheBench, the Perl API to Apache's ab
tool with added features that make it usable for regression testing as
well as benchmarking.
I am trying to keep up (catch up) with Apache's work on ab, so expect more
releases soon.
changes since 0.60:
* bugfixes:
-
stas01/10/22 01:33:48
Modified:ModPerl-Registry TODO
Log:
- document the rest of the nice to have things
Revision ChangesPath
1.4 +39 -7 modperl-2.0/ModPerl-Registry/TODO
Index: TODO
ged 01/10/20 23:50:06
Added: .email-etiquette.pod
Log:
Revision ChangesPath
1.1 modperl-site/email-etiquette.pod
Index: email-etiquette.pod
===
=head1 The mod_perl
dougm 01/10/22 11:19:35
Modified:.Makefile.PL
Log:
need touch dummy libmodperl.lib for win32 WrapXS/ Makefile.PLs
Revision ChangesPath
1.50 +12 -0 modperl-2.0/Makefile.PL
Index: Makefile.PL
[EMAIL PROTECTED] wrote:
ged 01/10/20 23:50:06
Added: .email-etiquette.pod
Log:
Revision ChangesPath
1.1 modperl-site/email-etiquette.pod
Index: email-etiquette.pod
Now Ged, after committing something to modperl-site you
dougm 01/10/22 10:20:11
Modified:lib/ModPerl WrapXS.pm
src/modules/perl modperl_config.c modperl_config.h
Log:
wrap all references to perl_module inside macros that are redefined
to call functions in .xs modules under WIN32 to avoid referencing perl_module
dougm 01/10/22 10:25:39
Modified:xs/tables/current/ModPerl FunctionTable.pm
Log:
sync
Revision ChangesPath
1.40 +25 -1 modperl-2.0/xs/tables/current/ModPerl/FunctionTable.pm
Index: FunctionTable.pm
dougm 01/10/22 11:02:29
Modified:t/hooks/TestHooks trans.pm
Log:
temp workaround for win32 problem with /TestFoo::bar urls
Revision ChangesPath
1.3 +13 -1 modperl-2.0/t/hooks/TestHooks/trans.pm
Index: trans.pm
16 matches
Mail list logo
