I've recently faced the problem. I've implemented some collaborative work
on my app. I've used the Channel API and it works really fine on localhost.
After deploy, the "update" in the other client is never received. why?
--
You received this message because you are subscribed to the Google Grou
Hi,
Do you still have this issue?
Are you sending and receiving messages from the same application version?
On Sun, Dec 30, 2012 at 12:00 PM, <091420...@umt.edu.pk> wrote:
> I've recently faced the problem. I've implemented some collaborative work
> on my app. I've used the Channel API and it
I can confirm this issue. It is there from August, it was the first time I
noticed at least. For us it looks like this - everything connected and
works, messages flow, then all of a sudden w/o any pattern in time or any
other conditions, client simply stops receiving any messages. No callbacks,
http://code.google.com/p/googleappengine/issues/detail?id=4940
On Fri, Jan 4, 2013 at 9:15 AM, Aleksei Rovenski
wrote:
> I can confirm this issue. It is there from August, it was the first time I
> noticed at least. For us it looks like this - everything connected and
> works, messages flow, then
I see 400 SID errors, but it seems not to be critical, because we are able
to recover easily, there is onerror callback called and client simply
creates new channel, no big deal.. Much worse is when client and server do
not know about the problem as I described above..
пятница, 4 января 2013 г.
btw those are 2 issues I would like to be fixed, please star them:
Add timestamp to channel presence notifications
http://code.google.com/p/googleappengine/issues/detail?id=8151
Channel API batch send method
http://code.google.com/p/googleappengine/issues/detail?id=4506
:D
пятница, 4 января 2013
This is exactly my experience. I would recommend to anyone considering use
of the Channel APIs that they find an alternative.
- Kris
On Friday, January 4, 2013 12:15:33 AM UTC-8, Aleksei Rovenski wrote:
>
> I can confirm this issue. It is there from August, it was the first time I
> noticed at
problem is onerror callback is not being always called so the client
isn't given a chance to recover. that turns out to be a big deal.
On Fri, Jan 4, 2013 at 9:31 AM, Aleksei Rovenski
wrote:
> I see 400 SID errors, but it seems not to be critical, because we are able
> to recover easily, there is
