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:
- fix
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
> 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 w
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 perl
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 i
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 p
> > 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
>
* 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?
* 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,
