> On Sep 23, 2014, at 3:25 PM, Yaron Goland <[email protected]> wrote: > > Makes sense. We could fix this by just flipping to idle as soon as we get > back the response header from the server if there is no immediate body but > one thing at a time.
No, it doesn't make sense to switch to idle as soon as you get the response header, because you still don't know if you're caught up or not. You might be about to receive a response with changes in it, as soon as the next TCP packet arrives. I assume you're worried about the performance of sending the extra request. If so, you'd be better off implementing WebSocket support on the server side, since it's more efficient (comparable to the continuous feed.) --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/27D8A07C-6565-49CC-A31D-2B5DD82842A6%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
