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 data is fed to it, via the Google Channel API, from a separate appengine app. I want this second appengine app to be able to pump the same information to my running phone session. I thought it would be nice to use the Google Channel API to do this. So basically the second app engine app is broadcasting messages down a channel, and both the map, and the running phone session, are picking up the messages and "displaying" them in their own way.
Assuming this approach makes any sense, then I need my Tropo App to be to be able to field these Channel API messages. That's why I thought of Javascript, and node.js. But in looking around on stackoverflow, I saw the mention you made of AppengineJS. I think I'll check that out. BTW, I've already got this working with the Tropo app just doing http fetches, and it's working tolerably well, but I wanted to explore other approaches. On Jul 3, 10:52 pm, Robert Kluin <[email protected]> wrote: > 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. > > Robert > On Jul 3, 2011 9:09 AM, "egilchri" <[email protected]> wrote: -- 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.
