Prev: MAXIMO Requirements in Austin, TX.,- duration 6+ months - Interviews over Phone
Next: Comparable Interface
From: Arne Vajhøj on 16 Jun 2010 23:02
On 16-06-2010 12:10, Paul Cager wrote:
> On Jun 16, 2:46 am, Arne Vajh�j<a...(a)vajhoej.dk> wrote:
>> On 15-06-2010 13:52, New Java 456 wrote:
>>
>>> Can anyone advise me on timeouts for Apache, WebLogic, et al?
>>> Basically, how long can a client block waiting for data from the
>>> server. (like PASV mode in FTP?).
>>
>> A very long time.
>>
>> Otherwise long poll would not work.
>
> Yes, although if you've got an HTTP proxy between the client and
> server you _might_ find that the proxy resets the connection if it
> doesn't see a response for a long time.

Those proxys can not be very popular today.

They will break a lot of AJAX code.

Arne

From: Paul Cager on 17 Jun 2010 05:43
On Jun 17, 4:02 am, Arne Vajhøj <a...(a)vajhoej.dk> wrote:
> On 16-06-2010 12:10, Paul Cager wrote:
[...]
> > Yes, although if you've got an HTTP proxy between the client and
> > server you _might_ find that the proxy resets the connection if it
> > doesn't see a response for a long time.
>
> Those proxys can not be very popular today.
>
> They will break a lot of AJAX code.
>
> Arne

I believe they are still popular (at least with the network
administrators) in some institutions that like to maintain a lot of
control over their users - e.g. employers, some universities, etc. And
in some countries it is normal for ISPs to use a transparent proxy for
their domestic broadband customers (I can't remember if it is Italy or
Spain where that's still the norm).

http://www.visolve.com/squid/squid30/timeout.php suggests that Squid
has a default read timeout of 15 minutes.

But you can write your Ajax code to be resilient to unexpected
connection reset. If the proxy's timeout is small compared to the
frequency of messages sent to the client then you'll be generating
extra HTTP traffic of course.
From: Arne Vajhøj on 17 Jun 2010 20:22
On 17-06-2010 05:43, Paul Cager wrote:
> On Jun 17, 4:02 am, Arne Vajh�j<a...(a)vajhoej.dk> wrote:
>> On 16-06-2010 12:10, Paul Cager wrote:
> [...]
>>> Yes, although if you've got an HTTP proxy between the client and
>>> server you _might_ find that the proxy resets the connection if it
>>> doesn't see a response for a long time.
>>
>> Those proxys can not be very popular today.
>>
>> They will break a lot of AJAX code.
>
> I believe they are still popular (at least with the network
> administrators) in some institutions that like to maintain a lot of
> control over their users - e.g. employers, some universities, etc. And
> in some countries it is normal for ISPs to use a transparent proxy for
> their domestic broadband customers (I can't remember if it is Italy or
> Spain where that's still the norm).
>
> http://www.visolve.com/squid/squid30/timeout.php suggests that Squid
> has a default read timeout of 15 minutes.
>
> But you can write your Ajax code to be resilient to unexpected
> connection reset. If the proxy's timeout is small compared to the
> frequency of messages sent to the client then you'll be generating
> extra HTTP traffic of course.

15 minutes is probably OK.

The user will be bored and browsing to somewhere else before that.

Arne


From: Paul Cager on 21 Jun 2010 05:10
On Jun 18, 1:22 am, Arne Vajhøj <a...(a)vajhoej.dk> wrote:
> On 17-06-2010 05:43, Paul Cager wrote:
....
> >http://www.visolve.com/squid/squid30/timeout.phpsuggests that Squid
> > has a default read timeout of 15 minutes.
>
> > But you can write your Ajax code to be resilient to unexpected
> > connection reset. If the proxy's timeout is small compared to the
> > frequency of messages sent to the client then you'll be generating
> > extra HTTP traffic of course.
>
> 15 minutes is probably OK.
>
> The user will be bored and browsing to somewhere else before that.
>
> Arne

It depends on the nature of your application, I guess. If it was a
mail reader then 15 minutes without an update isn't unusual.
From: Lew on 21 Jun 2010 08:20
Arne Vajhøj wrote:
>> 15 minutes is probably OK.
>>
>> The user will be bored and browsing to somewhere else before that.

Paul Cager wrote:
>> Arne
>

Don't quote sigs.
> It depends on the nature of your application, I guess. If it was a
> mail reader then 15 minutes without an update isn't unusual.

Apples and oranges. The discussion was about length of time for a response
from the server to a client request, not intervals between client requests.

--
Lew
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: MAXIMO Requirements in Austin, TX.,- duration 6+ months - Interviews over Phone
Next: Comparable Interface