Re: extending Allegroserve time-out period

--===============0673597796445843954==
Content-Type: multipart/alternative; boundary=Apple-Mail-1--188044113


--Apple-Mail-1--188044113
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=ISO-2022-JP;
	delsp=yes;
	format=flowed

Kamen,
     Thanks for the link!
It clears up many issues regarding timeouts.
Is there a way to get PortableAserve on Lispworks to run the
ACL 6.1 way rather than the ACL 6.0 way?
I've noticed that the *http-response-timeout*
defaults to 120,  which is associated with the
ACL 6.0 way.  I've set *http-response-timeout*
to be much higher,  480,  with good results,
but basing timeouts on individual socket
operations as supported by ACL 6.1 seems a much better
design.

Lawrence Au
Q-Phrase LLC



On Oct 12, 2006, at 4:55 AM, Kamen TOMOV wrote:

> On $B'c'b'q'U'Q(B, $B'0'\'d'`'^'S'b'Z(B 11 2006, Lawrence Au wrote:
>
>>     I've got a slow back end executable
>> producing new files that I need to serve,  and it takes
>> about 20 to 45 seconds for it to complete.
>> Meanwhile,  my PortableAserve
>> thread times out and I get a
>> NET.ASERVE::STREAM-ERROR-IDENTIFIER
>> error in the aserve-worker thread.
>>
>>    Is there a way to extend the
>> time-out period to 45 seconds?
>> I'm using PortableAserve on Lispworks.
>
> Have you tryied to change the timeouts specified in the Aserve
> documentation?
>
> http://www.franz.com/support/documentation/8.0/doc/aserve/ 
> aserve.html#timeouts
>
> HTH,
>
> -- 
> Kamen TOMOV
>
> _______________________________________________
> lispweb mailing list
> [email protected]
> http://www.red-bean.com/mailman/listinfo/lispweb

--Apple-Mail-1--188044113
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
	charset=ISO-2022-JP

Kamen,

    Thanks for the link!

It clears up many issues regarding timeouts.

Is there a way to get PortableAserve on Lispworks to run the

ACL 6.1 way rather than the ACL 6.0 way?

I've noticed that the *http-response-timeout*

defaults to 120,  which is associated with the

ACL 6.0 way.  I've set *http-response-timeout*

to be much higher,  480,  with good results,

but basing timeouts on individual socket

operations as supported by ACL 6.1 seems a much better

design.


Lawrence Au

Q-Phrase LLC




On Oct 12, 2006, at 4:55 AM, Kamen TOMOV wrote:


<excerpt>On
<fontfamily><param>Lucida Grande</param>$B'c'b'q'U'Q(B</fontfamily>, <fontfamily><param>Lucida Grande</param>$B'0'\'d'`'^'S'b'Z(B</fontfamily>
11 2006, Lawrence Au wrote:


<excerpt>    I've got a slow back end executable

producing new files that I need to serve,  and it takes

about 20 to 45 seconds for it to complete.

Meanwhile,  my PortableAserve

thread times out and I get a

NET.ASERVE::STREAM-ERROR-IDENTIFIER

error in the aserve-worker thread.


   Is there a way to extend the

time-out period to 45 seconds?

I'm using PortableAserve on Lispworks.

</excerpt>

Have you tryied to change the timeouts specified in the Aserve

documentation?


http://www.franz.com/support/documentation/8.0/doc/aserve/aserve.html#timeouts


HTH,


-- 

Kamen TOMOV


_______________________________________________

lispweb mailing list

[email protected]

http://www.red-bean.com/mailman/listinfo/lispweb

</excerpt>
--Apple-Mail-1--188044113--



--===============0673597796445843954==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
lispweb mailing list
[email protected]
http://www.red-bean.com/mailman/listinfo/lispweb

--===============0673597796445843954==--