Hi, There's a known bug that means the Channel API can't currently be used from backends. It should be fixed shortly. In the meantime, as a workaround, you could make a URLFetch to a frontend instance which will call the channel API on your behalf.
-Nick Johnson On Fri, May 27, 2011 at 6:31 AM, Chiguireitor <[email protected]>wrote: > Hello, i'm currently implementing a game and have noted in another > discussion that channels can't be served from a backend if they were > opened from the "frontend" (i.e. the standard user requests). > > I've currently made a test where i open a channel from the backend and > pass the token to the frontend via a memcache'd string, and the > "frontend" sends the corresponding token to the user agent. > > The channel then is opened normally, and everything goes ok, but no > data can be sent from the backend to the channel, and even worse, the > backend begins failing with this error: > > File "...\google\net\proto\ProtocolBuffer.py", line 485, in skipData > raise ProtocolBufferDecodeError, "corrupted" > ProtocolBufferDecodeError: corrupted > > And no data reaches the user end. After that the backend continues > working correctly, but no data ever reaches the frontend... > > > Please... help :-( > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Nick Johnson, Developer Programs Engineer, App Engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
