Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-Id: <1FFBA351-9EDF-4E7D-88E2-FEC9C64B8269@apache.org>
From: Damien Katz <damien@apache.org>
To: user@couchdb.apache.org
In-Reply-To: <b66ddc900903140536i49ede800xedac02f19d6fcf9a@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Use couchdb as the data store for real-time chat room
Date: Sat, 14 Mar 2009 09:11:23 -0400
References: <b66ddc900903140320u5bdbf3ffoaed76f332899c45e@mail.gmail.com>
 <49BBA112.3090700@gmx.de>
 <b66ddc900903140536i49ede800xedac02f19d6fcf9a@mail.gmail.com>

Erlang's speciality is lots of concurrent users.

We are planning to provide a native COMET mechanism, so clients can be  
notified as soon as documents they are interested are updated or  
created. The enhancements are for selective and near real-time  
replication features we are planning, but they will be useful for  
things like this too.

-Damien

On Mar 14, 2009, at 8:36 AM, howard chen wrote:

> Hi,
>
> On Sat, Mar 14, 2009 at 8:20 PM, Sven Helmberger <sven.helmberger@gmx.de 
> > wrote:
>
>> This sounds like it could be the main performance problem. I would  
>> expect
>> some form of COMET or even the long request pattern to improve your
>> performance.
>>
>
>
> Yes, but we are serving many concurrent users, so I don't want to hold
> a persistence connection from the server to client. (we are using
> Apache2/pre_fork, mod_php)
>
> As since our polling interval is adaptive, is it quite easy to scale
> by adding servers currently.
>
> Howard