>
>
> Hmm not sure. Consider the following use case: client connects to a
> channel, some time later he goes offline and comes back, client sees that
> the token is still valid and reconnects, so far so good. Now on the server
> I'm tracking the list of connected users. Obviously what I expect
On September 3, 2012 10:52:55 Johan Euphrosine wrote:
> On Fri, Aug 31, 2012 at 9:28 PM, Pascal Patry wrote:
> > Hi,
> >
> > Channels on AppEngine are picky. There are multiple issues that I had to
> > work around for an application that is currently in production:
>
> Thanks for your feedback, p
>
> > 3. The implementation is different from the test and production server
>
> Care to elaborate? (file new Defect if necessary)
>
It's pretty clear to anyone working with the system more than casually that
the implementations are different. I'm not sure that's really a problem; I
mean, th
I thought the Channel API was already based on web sockets (for platforms
that support them).
- Kris
On Sunday, September 2, 2012 3:31:31 PM UTC-7, vlad wrote:
>
> +1 Channels is probably the most overhyped but underwhelming feature on
> GAE. It was launched with lots of hype and high expectat
> > PS. One final thing I forgot to mention about Channel API problems is
> that
> > it seems some of the users simply can not load the channel javascript
> lib
> > which is hosted by google... What the hell...
>
> Are you refererring to:
> http://code.google.com/p/googleappengine/issues/de
Hi!
> I just escalated this bug to the Channel engineering team.
>
Very glad to hear this, thanks!
> >
> > - Sometimes channels are just dead
> > You create a channel, there are no errors or anything, but no matter how
> > many messages you send, it just won't receive any. The token is s
On Mon, Sep 3, 2012 at 10:36 AM, Aleksei Rovenski
wrote:
> I don't know what is your use case, but for mine Pusher is better by
> definition because it seamlessly supports broadcasting.
> So far I'm using it in parallel with google channels for not so important
> events and it looks good. It works
On Sun, Sep 2, 2012 at 10:16 AM, Aleksei Rovenski
wrote:
> Hi,
>
> I have to agree with Pascal. Channel API has too many issues and though I
> have worked around most of them to a certain degree when it started to be
> good enough, I would not repeat this if I would be still planning my
> applicat
On Fri, Aug 31, 2012 at 9:28 PM, Pascal Patry wrote:
> Hi,
>
> Channels on AppEngine are picky. There are multiple issues that I had to
> work around for an application that is currently in production:
Thanks for your feedback, please make sure you fill new
defects/feature requests or star existi
I don't know what is your use case, but for mine Pusher is better by
definition because it seamlessly supports broadcasting.
So far I'm using it in parallel with google channels for not so important
events and it looks good. It works through web sockets with fallback to
flash, but the stats I ga
Aleksei - please tell us how you go with Pusher.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/l7b3HdT6BdEJ.
To post to this group, send email to
y, September 02, 2012 3:32 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Channel API not working in production
+1 Channels is probably the most overhyped but underwhelming feature on
GAE. It was launched with lots of hype and high expectations. Still after 2
yea
+1 Channels is probably the most overhyped but underwhelming feature on
GAE. It was launched with lots of hype and high expectations. Still after 2
years to is mostly unusable. GAE team is better off killing Channels as a
feature to free up resources and focus on delivering websockets.
On Su
Hi,
I have to agree with Pascal. Channel API has too many issues and though I
have worked around most of them to a certain degree when it started to be
good enough, I would not repeat this if I would be still planning my
application. Some more issues that I can easily add to the list above:
-
On Friday, August 31, 2012 12:29:20 PM UTC-7, Pascal Patry wrote:
>
> Hi,
>
> Channels on AppEngine are picky. There are multiple issues that I had to
> work around for an application that is currently in production:
> 1. Channels aren't working on backends
>
Argh, seriously? That is a huge
Hi,
Channels on AppEngine are picky. There are multiple issues that I had to
work around for an application that is currently in production:
1. Channels aren't working on backends
2. No API is available to mobile
3. The implementation is different from the test and production server
4. Connection/
Hi All.
I've recently faced the same problem. I've implemented some collaborative
work on my app. I've used the Channel API in dev mode and it works really
fine. After deploy, I've tried to do the same actions as in development,
but the "update" in the other client is never recieved. I've added
Praveen,
Try asking this question on StackOverflow:
https://groups.google.com/forum/?fromgroups#!topic/google-appengine/Z6XN_64cA7w
Also, it would be helpful to provide more details when you do. "It sucks"
is terrible information. That kind of feedback is not actionable.
--
Ikai Lan
Developer P
I have implement struts based chat application using channel API
trying to implement the chat application., The Sample struts chat
application works in local enviroinment .But in production
enviroinment totally it sucks.Please help
--
You received this message because you are subscribed to the Go
19 matches
Mail list logo
