Someone pointed me to checking the connection class
for an abort. I found info on this in the modperl cookbook..That seems
useful if you want to server your own files, but would take a lot of overhead if
you had to continue to check it for a large file. It would not really do
me any good to
Hi!
On Sat, Nov 29, 2003 at 02:00:18AM -0600, John Michael wrote:
Someone pointed me to checking the connection class for an abort. I found
info on this in the modperl cookbook..That seems useful if you want to
server your own files, but would take a lot of overhead if you had to
continue to
But This:
if ($h-r-connection-aborted) {
would not be called until this
$h-r-send_fd($fh);
were already through. For a large file, wouldn't that it too late.
or would a real aborted connection cause send_fd($fh) to go ahead and stop
sending the file.
I've been reading through the cookbook
Hi!
On Sat, Nov 29, 2003 at 02:49:20AM -0600, John Michael wrote:
But This:
if ($h-r-connection-aborted) {
would not be called until this
$h-r-send_fd($fh);
were already through. For a large file, wouldn't that it too late.
or would a real aborted connection cause send_fd($fh) to
I think I may have it. I'm trying to limit
users to a certain folder to only 1 connection at a time. I'm going to
keep a list of active connections.
DO I just write the access handler and at some
point in the handler add the cleanuphandler
sub handler {
# code to check for active
Hi there,
On Sat, 29 Nov 2003, John Michael wrote:
I'm trying to limit users to a certain folder to only 1 connection at a time.
You've read the stuff that Randal's done I take it?
http://www.stonehenge.com/merlyn/LinuxMag/col17.html
There have also been several thread on this List which
Am Sa, 2003-11-29 um 09.49 schrieb John Michael:
But This:
if ($h-r-connection-aborted) {
would not be called until this
$h-r-send_fd($fh);
were already through. For a large file, wouldn't that it too late.
or would a real aborted connection cause send_fd($fh) to go ahead and stop
I'm pleased to announce the release of Bricolage 1.6.8. This maintenance
release addresses a few issues discovered since the release of version
1.6.7. Here is the complate list of chnages for this release:
* Custom select fields now correctly pay attention to the size
attribute.
