Re: serving very large files from allegroserve

Nick Levine wrote:

> So, what I really want to know, now that I've wasted over two hours
> digging into this (and everyone on this list has had to listen to me
> doing it), is: where did I go wrong?

There are places where you can change the behavior of the directory
entity but if you did none of that and just did a vanilla
publish-directory then I'm not sure how the timeout could
be nil.  Perhaps you can see some pattern in the file
entities that ended up with a nil timeout and that would
offer a clue.

I see that webactions isn't handling the timeout argument
(but then again webactions is mainly used to handle html files).

You can also set *http-response-timeout* to a large value
so that even if the entity gets a nil timeout you can
still have a large timeout.