> On Oct 24, 2014, at 1:35 PM, Seung Chan Lim <[email protected]> wrote: > > I'm trying to use longpoll with a call to > http://lite.couchbase./_active_tasks <http://lite.couchbase./_active_tasks> > instead of continuous. Why? Because with continuous it keeps appending to the > http response buffer, which can grow indefinitely.
There isn't a longpoll option for that. You just GET /_active_tasks without the "continuous" flag. > The question I have is how can I make a call to _active_tasks with longpoll > such that each subsequent call "advances" the responses? The behavior I see > now is that it just repeats itself. It doesn't "move on" to the next bits of > information. It returns the entire list of active tasks immediately. You'd have to set up a timer to poll it periodically, i.e. every few seconds. It's probably more efficient to keep using the 'continuous' mode, but close and re-open the connection once in a while to avoid building up too big a response buffer. —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/B3A7EF17-749C-4CED-AA31-A84406A9FB27%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
