[Seaside] Correct usage of Comet

Boris Popov boris at deepcovelabs.com
Tue Apr 14 17:11:05 UTC 2009

Some might find this interesting,



DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message header.
Unless otherwise indicated, it contains information that is private and
confidential. If you have received it in error, please notify the sender
and delete the entire message including any attachments.

Thank you.
-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Lukas
Sent: Monday, April 13, 2009 8:52 AM
To: Seaside - general discussion
Subject: Re: [Seaside] Correct usage of Comet

> Is it the network.http.max-connections-per-server key in Firefox
> that controls this? The default in the latest Firefox is set to 15,
> this key. I also found network.http.max-persistent-connections-
> per-server which is set to 18.

I don't remember which value this is. It certainly used to be much
lower a few years ago.

> Now if I can hijack part of you thread, I would like to know if anyone
> has experience with more heavy Comet load, like tens or hundred of
> listeners and several messages to each in a second? Could typical
> intel server running Seaside handle something like that?

I can't tell, because I don't know of anybody that used it in
production. The implementation is very lightweight though. On the
server an open socket and a few associated objects are consumed per


Lukas Renggli
seaside mailing list
seaside at lists.squeakfoundation.org

More information about the seaside mailing list