Chris Anderson wrote:
The next step on the roadmap is to give the ability to filter the
comet notifications with a JavaScript function. This code should not
be too hard to write but I doubt I'll have time to get to it this
week. There are a few other people who are capable of adding the
function,
http://jchrisa.net/drl/_all_docs_by_seq also has gaps, see 371 in here.
The coolest thing that could happen to _changes right now is a
multi-part mime encoding so we could stream attachments on the same
connection as documents for true continuous replication.
On Sat, May 30, 2009 at 9:29 PM, Pau
On Sat, May 30, 2009 at 11:48 PM, Randall Leeds wrote:
> On Tue, May 26, 2009 at 11:22, Chris Anderson wrote:
>>
>> There are other parts of the story we could add but haven't. For
>> instance, it should be possible to do a long poll on a particular
>> document URL if you are waiting for it to be
On Tue, May 26, 2009 at 11:22, Chris Anderson wrote:
>
> There are other parts of the story we could add but haven't. For
> instance, it should be possible to do a long poll on a particular
> document URL if you are waiting for it to be modified. Also,
> replication should be able to run against t
On Tue, May 26, 2009 at 3:11 AM, eric casteleijn
wrote:
Would the comet notifications supersede the (currently implemented) db
update notifications as well? Are there any estimates as to when that
would come around.
>>>
>>> Pretty sure the idea is to replace the current system'
Would the comet notifications supersede the (currently implemented) db
update notifications as well? Are there any estimates as to when that
would come around.
Pretty sure the idea is to replace the current system's functionality.
I'm not sure if that means update_notification will go away or n
>> If you mean in trunk, I'm not sure but I doubt it. If for no other
>> reason than if we added such a feature to trunk it'd be a signal that
>> we intend to support it for a very long time when we're already acting
>> on plans to replace it.
>>
>>> If not, we'll just keep using the patch interna
On Apr 8, 2009, at 2:44 PM, Paul Davis wrote:
On Wed, Apr 8, 2009 at 2:15 PM, Devendra Gera
wrote:
Hi Paul,
Thanks for taking the time to review the patch.
On Wed, 08 Apr 2009, Paul Davis wrote:
Gera,
That looks like a solid patch, but unfortunately I think that the
comet notification w
On Wed, Apr 8, 2009 at 2:15 PM, Devendra Gera wrote:
> Hi Paul,
>
> Thanks for taking the time to review the patch.
>
> On Wed, 08 Apr 2009, Paul Davis wrote:
>
>> Gera,
>>
>> That looks like a solid patch, but unfortunately I think that the
>> comet notification will end up superseding the functi
Hi Paul,
Thanks for taking the time to review the patch.
On Wed, 08 Apr 2009, Paul Davis wrote:
> Gera,
>
> That looks like a solid patch, but unfortunately I think that the
> comet notification will end up superseding the functionality. The
> basic ideas of the comet framework are to post a Ja
Gera,
That looks like a solid patch, but unfortunately I think that the
comet notification will end up superseding the functionality. The
basic ideas of the comet framework are to post a JavaScript function
to the server to allow clients to filter db updates. I'm pretty sure
this is under active d
Hi,
Although I am not an active participant of this list at the moment,
I'd vote in support of this patch. I see some use of it in one of my
projects.
Thanks.
On Wed, Apr 8, 2009 at 7:05 AM, Devendra Gera wrote:
> In order to achieve a single-step publish process, I wanted a hook into
> CouchD
Hi,
This is my first message to this mailing list. Please direct me to the
right place if this isn't it.
We are planning to use CouchDB as a central store for objects which also
need to be pushed to various nodes. These nodes get the objects, work on
them and then update them at the central stor
13 matches
Mail list logo
