[google-appengine] Re: Channel API alternatives

Strom, We're recommending Firebase as an alternative to the Channel API. Please have a look at this article on how to use it with App Engine: https://cloud.google.com/solutions/using-firebase-real-time-events-app-engine. As it connects to all manner of clients (web, Android, iOS), we believe

[google-appengine] Re: Channel API alternatives

How nice, another piece of GAE being shut down. As for alternatives, I've found the following four that I'll be looking into: * https://pusher.com/ * https://www.pubnub.com/ * https://www.ably.io/ * https://framework.realtime.co/ On Sunday, October 30, 2016 at 3:58:41 AM UTC+2, PK wrote: > > Goo

Re: [google-appengine] Re: Channel API alternatives

Hello Alexey, You are correct that Pub/Sub is not a complete replacement to the Channel API, and was recommended as a simple lightweight callback communication alternative. The intended replacement is indeed Firebase. As you mentioned, Pub/Sub is designed for pre-defined Topic/Subscriptions,

Re: [google-appengine] Re: Channel API alternatives

Hi Alexey, this has been my understanding too but have never had direct experience with it. I was surprised that Google Support suggested it as an alternative. I still do not think it is. PK > On Nov 3, 2016, at 4:49 PM, 'Alexey' via Google App Engine > wrote: > > Cloud Pub/Sub works only

Re: [google-appengine] Re: Channel API alternatives

Cloud Pub/Sub works only between servers -- it doesn't seem like there's server-to-browser push functionality with this, correct? Also, this is explicitly meant for static topic, whereas the old Challen/XMPP stack supported ad-hoc and stateless topic/channel selection and a push from server to

Re: [google-appengine] Re: Channel API alternatives

Google Cloud Pub/Sub makes use of Topics and Subscribers. Publishers post messages to a Topic, and the message is either Pushed or Pulled to/by the Subscribers w

Re: [google-appengine] Re: Channel API alternatives

Thanks Jordan. How were you thinking that pubsub will work all the way out to the browsers? Thanks, PK p...@gae123.com PS I could write a lot about the first two sentences of your response but I will skip it. I will just say that it is ironic that a low usage platform like GCP makes such bold

[google-appengine] Re: Channel API alternatives

Our goal is to continue to do a better job of delivering reliable, performant, and full featured services. This means deprecating those APIs that have little to zero usage on our system to free up resources for newer, better performing products. The Channel API

[google-appengine] Re: Channel API alternatives

I was just discussing this very point with someone today. Firebase and Channel are not equivalent, which is why Google appears to be pushing this API change. Otherwise what is the point of having API, if implementation details cannot be addressed seamlessly? On Monday, October 31, 2016 at 5:2

Re: [google-appengine] Re: "Channel API Hours Used" quota exceeded

Thanks Jesse, I tuned my code and we will see how it goes. There seems to be an issue with some customers who keep failing to communicate over a channel and keep asking for a new channel. Other customers are fine. I still need to get to the bottom of this. Is the channel communication over ports

[google-appengine] Re: "Channel API Hours Used" quota exceeded

Hi PK, The "Channel API Hours Used" quota has to with the TTL (time to live) of the channels you are opening. In Python, this is the "duration_minutes" variable, and it defaults to two hours: https://cloud.google.com/appengine/docs/python/channel/functions. Note that enabling billing for your

[google-appengine] Re: Channel API Quota exception even though dashboard shows only 20% channels created...

This just started happening for me tonight as well, and I'm hardly using any channels. On Monday, January 30, 2012 12:00:49 AM UTC-8, Elias Naur wrote: > > Moishe: I'm still getting this error, which has effectively shut down > our app, browsertexting. Please see: > > http://code.google.com/p/g

[google-appengine] Re: Channel API - Channels Created Costs

We've been using the Channel API for a while and since March 2014 pricing changes (http://googlecloudplatform.blogspot.fr/2014/03/google-cloud-platform-live-blending-iaas-and-paas-moores-law-for-the-cloud.html) Channel created are free. They used to be priced at 1 cent for 100 created, which app

[google-appengine] Re: Channel API - Channels Created Costs

You can use appstats to find out and calculate costs for any of your GAE handlers/functions. A quick test reveals that creating a channel costs 10,000 micro-pennies (1 dollar equals 100 pennies, 1 penny equals 1 million micropennie

[google-appengine] Re: Channel API javascript memory leak

I just ran into a second problem with reopenning a second Channel in javascript, and this one is much more of a pain. My Javascript uses various parts of the history API (history.go, history.pushState, window.onpopstate) When a channel times out and I create a new channel, extra history state a

[google-appengine] Re: channel api not working on production

Hello Glen, As you can see from this lengthy discussion you've dug up, the Channel API can be quite temperamental, mildly speaking. I'm sorry to tell you that there is really no magic bullet solution, that's just the way that Channel API is right now. However, here are a few solutions you migh

[google-appengine] Re: channel api not working on production

We are currently facing a similar problem where the client stops receiving messages from the server. What we have observed is the application will perform as expected, receiving messages opening up the channel on the initial few visits, however after a period of time the channel on the client w

Re: [google-appengine] Re: Channel API Javascript error Uncaught TypeError: Cannot call method 'ab' of null

@Lahiru Great tip, it seems to have worked for me too. I'm also struggling with this error: Channel API - 400 Unknown SID Error, http://code.google.com/p/googleappengine/issues/detail?id=4940 Hopefully it will solve it too :-) Cheers! On Thu, Jan 17, 2013 at 7:09 AM, Lahiru Abeydeera wrote: >

[google-appengine] Re: Channel API Javascript error Uncaught TypeError: Cannot call method 'ab' of null

I found a work around. Try to remove the iframe added by channel api before re-connecting. $('#wcs-iframe').remove(); On Tuesday, January 15, 2013 7:30:40 AM UTC-8, Lahiru Abeydeera wrote: > > I got the exact same problem. Please let me know when somebody finds the > answer to this. > > Thanks

[google-appengine] Re: Channel API Javascript error Uncaught TypeError: Cannot call method 'ab' of null

I got the exact same problem. Please let me know when somebody finds the answer to this. Thanks On Saturday, January 12, 2013 11:44:49 AM UTC-8, Paulo Daniel Taylor de Carvalho wrote: > > > It just loops forever and this it what I can see in the Javascript console. > This error happens after a

[google-appengine] Re: Channel API Javascript error Uncaught TypeError: Cannot call method 'ab' of null

Try this link http://www.phonnix.com/channel.html Open the javascript console and keep clicking 'Open Channel' until you see the error. Note that this doesn't happen in the Dev server. Thanks! Paulo On Monday, January 14, 2013 9:07:41 PM UTC+1, Santiago wrote: > > Can you show us your code to

[google-appengine] Re: Channel API Javascript error Uncaught TypeError: Cannot call method 'ab' of null

Can you show us your code to have a better explanation of the context? Thanks On Saturday, January 12, 2013 5:44:49 PM UTC-2, Paulo Daniel Taylor de Carvalho wrote: > > > It just loops forever and this it what I can see in the Javascript console. > This error happens after a reconnect when I try

[google-appengine] Re: channel api not working on production

I've seen problems with the Channel API where both sides of the connection were "half open", i.e. each side believed there was a connection but messages would not be sent. I eventually replaced the Channel API with a node.js service running WebSockets. The GAE app posts messages to this servic

[google-appengine] Re: Channel API is working locally But not in production throws provided token is invalid

Did you ever figure out what was causing your issue? If so, it would be really helpful to others in the community if you could follow up and post what the problem was. Thank you, James On Tuesday, March 13, 2012 8:54:19 AM UTC-7, praveen kumar wrote: > > I will create channel Id(token) using

[google-appengine] Re: Channel API and "fan out" to multiple clients

This is very important, please someone from google confirm. Thanks On Monday, October 8, 2012 2:17:10 PM UTC-3, Andrew Mackenzie wrote: > > This overview page for the Channel API > > https://developers.google.com/appengine/docs/java/channel/overview > > states in the "Caveats" section: > > "Only

Re: [google-appengine] Re: Channel API and "fan out" to multiple clients

Thanks Aleksei. I tested on two or three clients only, across machines, browsers and users (geographies). I have starred the issue you linked to. Before seeing your post I submitted my own feature request here http://code.google.com/p/googleappengine/issues/detail?id=8242 so, maybe google will

Re: [google-appengine] Re: Channel API and "fan out" to multiple clients

I remember reading somewhere on StackOverflow that few connections maybe supported to one channel to support same user refreshing the page or smt like that.. How many connections did you test to one channel? If you want fan out, please star this issue: http://code.google.com/p/googleappengine/is

Re: [google-appengine] Re: Channel API and "fan out" to multiple clients

Seems pretty well defined here: https://developers.google.com/appengine/docs/java/channel/overview#Caveats "One Client Per Client ID Only one client at a time can connect to a channel using a given Client ID, so an application cannot use a Client ID for fan-out. In other words, it's not possibl

Re: [google-appengine] Re: Channel API and "fan out" to multiple clients

its undefined behavior. they never said it will not work or prohibited. they said undefined. On Tue, Oct 9, 2012 at 1:54 AM, Richard Watson wrote: > I'm sure it's very unlikely to work reliably. If you need that, until > Google makes a policy change I'd suggest using something like Pusher. > ht

[google-appengine] Re: Channel API and "fan out" to multiple clients

I'm sure it's very unlikely to work reliably. If you need that, until Google makes a policy change I'd suggest using something like Pusher. http://pusher.com/ On Monday, October 8, 2012 7:17:10 PM UTC+2, Andrew Mackenzie wrote: > > This overview page for the Channel API > > https://developers.go

[google-appengine] Re: Channel API future improvements?

This is logged here: http://code.google.com/p/googleappengine/issues/detail?id=7098 I patched the 1.7 channel API locally to deal with it; see the issue comments. On Saturday, March 5, 2011 8:02:23 AM UTC-8, Westmark wrote: > > Is there any way for the client to terminate the connection while

Re: [google-appengine] Re: Channel API and the development enviroment: Internet Explorer does not receive any messages

Can you file an issue on our issue tracker? Sorry if I missed, but I couldn't find any. Thanks, -- Takashi On Sun, Jun 24, 2012 at 10:41 PM, Heiko Roth wrote: > Hi folks, > > It's definitly not working for months now. Uploading it into an appengine > isn't a solution for development or debuggin

[google-appengine] Re: Channel API and the development enviroment: Internet Explorer does not receive any messages

Hi folks, It's definitly not working for months now. Uploading it into an appengine isn't a solution for development or debugging. It's just a work around. @Google When will you fix this issue? Thanks. -- You received this message because you are subscribed to the Google Groups "Google App En

Re: [google-appengine] Re: Channel API - Something I don't get messages even if I get "On Opened"

): didn't help thanks anyway On Thu, Jun 7, 2012 at 12:41 AM, Aleksei Rovenski < aleksei.roven...@gmail.com> wrote: > Hi, > > This looks like this one: > http://code.google.com/p/googleappengine/issues/detail?id=7239 > I don't see it happen a lot though... > > The only way I can suggest is to st

[google-appengine] Re: Channel API - Something I don't get messages even if I get "On Opened"

Hi, This looks like this one: http://code.google.com/p/googleappengine/issues/detail?id=7239 I don't see it happen a lot though... The only way I can suggest is to start a timer and if your app doesn't receive any messages in certain period, then try another channel, but it seems you are doing

Re: [google-appengine] Re: Channel API between front and backend instances

Star this issue: http://code.google.com/p/googleappengine/issues/detail?id=6726 I think it's the same problem. Cheers, -Andrin On Wed, Mar 14, 2012 at 7:04 PM, Jonathan Harris wrote: > Any news on this potential fix? > > On Thursday, 28 July 2011 19:56:22 UTC+1, Justin Haugh wrote: >> >> Not at

[google-appengine] Re: Channel API between front and backend instances

Any news on this potential fix? On Thursday, 28 July 2011 19:56:22 UTC+1, Justin Haugh wrote: > > Not at the moment, but we're working on a fix for this, so that a channel > created by a frontend can be used by a backend, and vice-versa. I can't > provide an exact release date at this point, bu

[google-appengine] Re: Channel API Quota exception even though dashboard shows only 20% channels created...

Moishe: I'm still getting this error, which has effectively shut down our app, browsertexting. Please see: http://code.google.com/p/googleappengine/issues/detail?id=6817 - elias On Jan 27, 6:07 pm, amit wrote: > Yes, this seems resolved. Thanks for all your help! > > On Jan 27, 7:14 am, Moishe

[google-appengine] Re: Channel API Quota exception even though dashboard shows only 20% channels created...

Yes, this seems resolved. Thanks for all your help! On Jan 27, 7:14 am, Moishe wrote: > This should be resolved now; it was related to the new channel_minutes > quota. Please post if you see any more problems with this. -- You received this message because you are subscribed to the Google Group

Re: [google-appengine] Re: Channel API Quota exception even though dashboard shows only 20% channels created...

This should be resolved now; it was related to the new channel_minutes quota. Please post if you see any more problems with this. -- 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.goog

Re: [google-appengine] Re: Channel API Quota exception even though dashboard shows only 20% channels created...

We are having the same problem and it is affecting production hard. python create_channel call fails. app-id: miumeet-hr (it should be a premier account by now) I have created a production issue, please star: http://code.google.com/p/googleappengine/issues/detail?id=6806 Cheers, -Andrin On Fr

[google-appengine] Re: Channel API Quota exception even though dashboard shows only 20% channels created...

Could you tell me your app-id? -- 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/-/7Fzl8RCXcbgJ. To post to this group, send email to google-appengine@

[google-appengine] Re: Channel API, Bugs on IE

Yep, same problem with IE7 where messages were not received. I'm now using polling and it's working like a charm. -- 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/goog

[google-appengine] Re: Channel API onError codes

does anyone know why it is that every time i try to go to "khanacademy.com" it gives me this error? Error: Server Error The server encountered an error and could not complete your request. If the problem persists, please reportyour problem and m

[google-appengine] Re: Channel API onError codes

For those who are interested: We did quite extensive testing on this and we figured out that in the onError JS Callback of a socket you can just close the current channel and reopen a new channel with the same channel id if error code is "0" or "-1". This means you can spare the expensive extra ne

[google-appengine] Re: Channel API JS partially broken

Do you have any details on what the server response to the script request is for these? A workaround might be directly requesting http[s]:// talkgadget.google.com/talkgadget/channel.js (the request to /_ah/ channel/jsapi redirects to this path) I'll investigate. -- You received this message bec

[google-appengine] Re: Channel API not working properly

http://www.help-live-chat.com is suffering too and the same error still persists after many errors. Keeping an eye out on the outage page but no activity there. On Sep 15, 3:05 pm, ShinTEZUKA wrote: > Me too... I got that error a few hours ago. But 7 hours ago, it woks > fine(in JAPAN). > And it

[google-appengine] Re: Channel API not working properly

I'm experiencing issues with the Channel API only being able to successfully send 1 message to my connected clients. After the one message is received any subsequent messages are not received by the client until I reestablish the socket connection? Is this related to this service outage? Client

Re: [google-appengine] Re: Channel API not working properly

OpenID service has also been down for us for about 6 hours or more. On 15 September 2011 21:12, Brian Immel wrote: > Same here... Started within the last day for me. > > > > > On Sep 15, 3:26 am, GK wrote: >> Same here. >> >> I have starred the issue. >> >> On Sep 15, 12:58 pm, Tom Newton wrote

[google-appengine] Re: Channel API not working properly

Me too... I got that error a few hours ago. But 7 hours ago, it woks fine(in JAPAN). And it doesn't work on Android too. On 9月15日, 午後3:12, Philip wrote: > I have had an app working with channels deployed to App Engine for a > while now. I have made some changes to the code and haven't isolated a

[google-appengine] Re: Channel API not working properly

Same here... Started within the last day for me. On Sep 15, 3:26 am, GK wrote: > Same here. > > I have starred the issue. > > On Sep 15, 12:58 pm, Tom Newton wrote: > > > > > > > > > Same here... Has been working flawlessly for a few months now. > > > Uncaught CustomError: Service for "ea" is

[google-appengine] Re: Channel API not working properly

Same problem is occured. via Chrome and Firefox from japan -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengi

[google-appengine] Re: Channel API not working properly

Yes, https://rogerth.at is also suffering from this exact problem. Please fix it asap, my customers are affected by this. On Sep 15, 11:12 am, Bay wrote: > Same problem... Channel API not working. Similar error as Philip -- You received this message because you are subscribed to the Google Gro

[google-appengine] Re: Channel API not working properly

It seems fixed now, or at least my app's channel feature started working. I agree with Bay, that there should be more test coverage / status reporting. I've been defending GAE even with the recent price increase drama, but it's getting hard with a 9 hour outage addition. My main defense of the pri

[google-appengine] Re: Channel API not working properly

Why dont you do what other services do: Write small apps that continously make sure that all the functions are working in production. Datastore puts, datastore reads, channel broadcasting, etc... Then you would have really quickly noticed that an issue was preventing the push-function from worki

[google-appengine] Re: Channel API not working properly

ETA is about 2 hours for complete rollout of fix. -- 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/-/LmmXiuBBFh0J. To post to this group, send email t

[google-appengine] Re: Channel API not working properly

Any ETA from Google to fix this issue. We are waiting on this one. -- 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/-/AIBc5uAm2iQJ. To post to this gr

[google-appengine] Re: Channel API not working properly

App Engine team is aware of this issue, and working on the fix. We'll update in the downtime notify group. -- Takashi Matsuo -- 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.

[google-appengine] Re: Channel API not working properly

So 6 hours of the Channel API being down and no word from Google. I wonder, would this fall under the SLA in the future? On Sep 15, 1:26 pm, GK wrote: > Same here. > > I have starred the issue. > > On Sep 15, 12:58 pm, Tom Newton wrote: > > > > > > > > > Same here... Has been working flawlessly

[google-appengine] Re: Channel API not working properly

Same here. I have starred the issue. On Sep 15, 12:58 pm, Tom Newton wrote: > Same here... Has been working flawlessly for a few months now. > > Uncaught CustomError: Service for "ea" is not registered is what I'm > seeing this morning. > > Have starred your ticket. > > T > > On Sep 15, 10:47 am

[google-appengine] Re: Channel API not working properly

Same here... Has been working flawlessly for a few months now. Uncaught CustomError: Service for "ea" is not registered is what I'm seeing this morning. Have starred your ticket. T On Sep 15, 10:47 am, Andrin von Rechenberg wrote: > I have filed a produciton issue ticket. > > Please star it so

Re: [google-appengine] Re: Channel API not working properly

I have filed a produciton issue ticket. Please star it so google gets aware about it: http://code.google.com/p/googleappengine/issues/detail?id=5903 The problem also appears on all mobile phones. This is clearly a bug on googles side. -Andrin On Thu, Sep 15, 2011 at 11:44 AM, Strom wrote: >

[google-appengine] Re: Channel API not working properly

Same here and it's not limited to chrome, doesn't work in IE9 either. On Sep 15, 12:41 pm, Andrin von Rechenberg wrote: > We are facing the same problem, > > Has anyone filed a production ticket? > > -Andrin, from MiuMeet > > > > > > > > On Thu, Sep 15, 2011 at 11:12 AM, Bay wrote: > > Same prob

Re: [google-appengine] Re: Channel API not working properly

We are facing the same problem, Has anyone filed a production ticket? -Andrin, from MiuMeet On Thu, Sep 15, 2011 at 11:12 AM, Bay wrote: > Same problem... Channel API not working. Similar error as Philip > > -- > You received this message because you are subscribed to the Google Groups > "Goog

[google-appengine] Re: Channel API not working properly

Same problem... Channel API not working. Similar error as Philip -- 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/-/8QTBSzn3vz0J. To post to this grou

[google-appengine] Re: Channel API not working properly

I am facing the same issue from today morning onwards. I am getting error in following URL: https://139.talkgadget.google.com/talkgadget/d?token=AHRlWrq-vS9cLNrNyVvqXp9QCrMOifivML_dS57svS7TAnJPXDarIUdQeeVLpwneZ6WkZhM-MISnN4odUesmAEgqqMIfxa0Y0srUBslOf92L2Qiw5GiXc1iSAUzSIDfSs6LuyGVieQjC90TQgkT2JuM

[google-appengine] Re: Channel Api for devloping multiplayer game

Hi Everson Alves da Silva I will definitely look into the new version of the app engine and see if my problem is resolved. I have one more question. If my request size is large then, is there any chance that the channels will disconnect automatically?? thanks, H

[google-appengine] Re: Channel API between front and backend instances

Not at the moment, but we're working on a fix for this, so that a channel created by a frontend can be used by a backend, and vice-versa. I can't provide an exact release date at this point, but it likely will be in one of the next few releases. Until then, the suggested method of handling thi

[google-appengine] Re: Channel Api for devloping multiplayer game

Hello Hariprasath, I recommend you first try it with the new release 1.5.2. Channel Api wasn't working for me in 1.5.1 and got fixed with the new release. Also, tokens expire after 2 hours. Jhonny Everson Creator of the 'Taking a Break' iPhone app for Facebook and Twitter http://takingabreaka

[google-appengine] Re: Channel API, and node.js

This could be a result of my imperfect understanding of the various pieces. I've got an app engine app that puts up a Google Map, and then allows the user to click a button and place a call using Phono.js. The call is fielded by a Tropo app. Meanwhile, the user clicks around on the Google Map, and

[google-appengine] Re: Channel API onOpen() not being hit every time.

Yep. Happens to me too.The initial connection of the channel fires the onOpen event, but subsequent connections using the same token does not. On Jul 4, 1:43 am, Eurig Jones wrote: > I have successfully created a simple prototype of use of the channel > API for myself, but on multiple openin

[google-appengine] Re: Channel API question about channel.open([token]) JS call

Sorry to keep adding to this, but I thought I should add the log of the connect/disconnect problem: 2011-07-04 03:57:44.424 /_ah/channel/disconnected/ 200 237ms 38cpu_ms 0kb I 2011-07-04 03:57:44.421 com.firstlightapps.MyApp.ChannelDisconnectedServlet doPost: client DISCONNECTED from channel: log

[google-appengine] Re: Channel API question about channel.open([token]) JS call

I'm still having a lot of other related problems with channels disconnecting. First of all, when the client disconnects from the channel (notified by Channel Presence) I do not get a onClose event fired on the socket. So, how can my client when he gets disconnected? Also, I'm having problems whe

[google-appengine] Re: Channel API question about channel.open([token]) JS call

Okay I think I figured this out already. I *think* I'm clear on the differences between connect/disconnect and creation/expiration of channels Basically there's no way to get notified or verify if a particular channel with ClientID has expired or not. What I did was create an Entity that stored

[google-appengine] Re: Channel API question about channel.open([token]) JS call

So, the Channel Presence feature actually notifies when a channel is connected/disconnected as opposted to created/destroyed? If this is correct, then how can I find out when the channel that was created on the server-side has been closed and not simply disconnected? I guess I'm confused about cr

Re: [google-appengine] Re: Channel API, and node.js

I don't understand the point in using another server runing node.js. Why not only use app engine (or only use node.is)? Even if everything runs fast, the few hundred ms of lag would be very noticable on the phone. If you must use both, I'd almost think using URL fetch would be better for latency.

[google-appengine] Re: Channel API, and node.js

I want to pickup realtime messages from App Engine, without polling. App Engine can send messages down the Channel API socket, and browsers can field them, in real time. I want these same messages to be picked up by a server that is listening using node.js. So I guess that requires a Channel API cl

[google-appengine] Re: Channel API - onMessage blocking?

Hi Chiguireitor, thanks. On Jun 16, 3:53 pm, Chiguireitor wrote: > Hi Halm, i'm currently building a queue to ensure sequential delivery > (adding buffering too). So, that means onMessage spawns a new thread? I.e. it is not assured that the before onMessage call is completed? > I suggest you t

[google-appengine] Re: Channel API - onMessage blocking?

Hi Halm, i'm currently building a queue to ensure sequential delivery (adding buffering too). I suggest you to do the same, because everytime you send a message, the connection needs to be restablished. -- You received this message because you are subscribed to the Google Groups "Google App En

[google-appengine] Re: Channel API and development server behavior

Here are my latest observations that explain earlier conflicting messages from me on this thread. After adding the timeout change, the behavior changes based on the browser. For chrome the workaround works fine. For Firefox 2.x and latest Safari on Mac it works for me only up to setting the timeout

Re: [google-appengine] Re: Channel API and development server behavior

Hi, In your code need to set the socket POLLING_TIMEOUT_MS. I've tested this, works correctly. goog.appengine.Socket.POLLING_TIMEOUT_MS = 5000; DevSocket is exported as Socket at the bottom of the jsapi file. Robert On Mon, Jun 6, 2011 at 23:48, PK wrote: > Issue 4946 http://code

[google-appengine] Re: Channel API and development server behavior

Issue 4946 http://code.google.com/p/googleappengine/issues/detail?id=4946 seems to be the same or closely related with what I reported here so please star it if you want to see a resolution. PK www.gae123.com -- You received this message because you are subscribed to the Google Groups "Google A

[google-appengine] Re: Channel API and development server behavior

It turns out that I spoke too soon about this. Probably I just did not properly refresh the browser when I said that changing the value from 500 to 5000 works; channel notifications do not work after such a change so this is not a workaround. PK -- You received this message because you are subsc

[google-appengine] Re: Channel API and development server behavior

Once more, thanks Robert for pointing this out. I patched the value to 5000 from the original value of 500 and things are much better... PK www.gae123.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email t

Re: [google-appengine] Re: Channel API and development server behavior

Have you tried setting the polling timeout? goog.appengine.DevSocket.POLLING_TIMEOUT_MS http://code.google.com/p/googleappengine/source/browse/trunk/python/google/appengine/tools/dev-channel-js.js#5234 Robert On Fri, Jun 3, 2011 at 13:23, PK wrote: > Thanks Nick. > > Is so frequent poll

[google-appengine] Re: Channel API and development server behavior

Thanks Nick. Is so frequent polling really necessary though? My feedback is that you need to look at this implementation again. In my app, I would be fine to wait up to 5-15 seconds for channel notifications on the dev server. If other apps are more sensitive maybe the interval can be made config

[google-appengine] Re: Channel API & Adobe AIR

Filed as issue 4973 (http://code.google.com/p/googleappengine/issues/ detail?id=4973) On May 3, 5:19 pm, GK wrote: > Hi, > my tests show that under AIR the hidden iframe is created and points > athttp://talkgadget.google.com. > I'll also file this issue. > > I'll be happy to provide any further a

[google-appengine] Re: Channel API & Adobe AIR

Hi, my tests show that under AIR the hidden iframe is created and points at http://talkgadget.google.com. I'll also file this issue. I'll be happy to provide any further assistance in identifying this problem. Thanks! Guy. On May 2, 5:30 pm, Moishe wrote: > There shouldn't be a need for a local

[google-appengine] Re: Channel API & Adobe AIR

There shouldn't be a need for a locally patched bundle anymore; the patch is being served live in production now. So the AIR problem you're encountering must be something different. I'll try to take a look at it soon; in the meantime could you please file an issue here: http://code.google.com/p/g

[google-appengine] Re: Channel API offline messages

On 11 Кві, 09:33, Robert Kluin wrote: > As I recall, messages sent to a channel who's client is disconnected are > silently dropped.  Adding presence to the Channel API is on the roadmap. > http://code.google.com/appengine/docs/roadmap.html Oh... too bad. Even with presence it will make just li

[google-appengine] Re: Channel API broken in Chrome Extensions

Moishe, Glad to hear it and thanks for the quick follow-up. I'll send you an email shortly for the static file. I wonder, is it generally possible/wise to use a static file in order to ensure predictable reliability? I.e. as with jquery served from the Google Libraries API, I can get the versi

[google-appengine] Re: Channel API broken in Chrome Extensions

Okay, I've identified and fixed the problem, and am working on getting a fix rolled out to production. No ETA on that yet. In the meantime if you'd like a patched jsapi file that you can serve statically from your own site, contact me directly at moishel at google.com. -- You received this messa

[google-appengine] Re: channel api multiple connect to the same channel

Hi, I believe that the polling only happens in the local development environment - on the Production servers, it uses the persistent connection. Cheers, Simon -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send em

[google-appengine] Re: Channel API broken in Chrome Extensions

I have the same problem here, trying to use an App Engine Channel from a Chrome extension fails to trigger onmessage/onopen/onerror. Nothing happens, and there's nothing in the extension background page console log. It worked fine a few days ago, and I haven't changed any extension code in that tim

[google-appengine] Re: Channel API broken in Chrome Extensions

Hi Moishe, I am using the stable release, and the current up-to-date version is 10.0.648.204 (on a Mac). I only use the Channel API within a chrome extension, so I can't say if there's a problem in other cases. -Ronald. -- You received this message because you are subscribed to the Google

[google-appengine] Re: Channel API broken in Chrome Extensions

Hi, Ronald. I'm looking into this today, will try to get back to you later on with some more information. Is this only happening with Chrome extensions? Which channel of Chrome are you running - dev, beta or main? Thanks! -Moishe -- You received this message because you are subscribed to the G

[google-appengine] Re: Channel API encoding problem

Dilbert, I know it is early to recommend this, however there is another Channel API service that supports UTF8 and Unicode encodings called PubNub. The pricing structure is different so go to http://www.pubnub.com to learn more about the offering. There are other Channel API services out there th

[google-appengine] Re: Channel API encoding problem

I have tried on production server and everything is fine, so this is only dev server problem. You can close that issue if it will be fixed in 1.4.3. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to googl

[google-appengine] Re: Channel API encoding problem

Yes Moishe I found the problem on the dev appserver. I will try to reproduce it on the production servers later and let You know. BTW I reported the issue here: http://code.google.com/p/googleappengine/issues/detail?id=4675 -- You received this message because you are subscribed to the Google

[google-appengine] Re: Channel API encoding problem

Is this just on the dev appserver? There is a known bug that the encoding isn't set properly that'll be fixed in 1.4.3. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com.

  1   2   >