Ok, I see. My devious plan is to circumvent all the webfilters out there which are already blocking talkgadget.google.com due to Google Talk. I have several friends stuck behind such filters and they want to be able to use all the features on my site. So I was hoping that my domain could act as a proxy in front of talkgadget.google.com so the filter does not block it.
BR // Fredrik On Wed, Mar 23, 2011 at 5:48 AM, Nick Johnson (Google) < nick.john...@google.com> wrote: > Hi Fredrik, > > This isn't possible - the Channel API provides a service that isn't > available otherwise through App Engine - if you could serve it yourself, > there'd be no need for the Channel API. > > What are you trying to accomplish? > > -Nick Johnson > > On Wed, Mar 23, 2011 at 4:32 AM, Westmark <fredrik.westm...@gmail.com>wrote: > >> Hi! >> >> I was just wondering how much of problem it would be to add the >> possibility to serve the channel API through your own app instead of >> via talkgadget.google.com. Kind of like how you serve the Remote API >> by adding the handler to your app.yaml without actually writing any >> code for it. >> >> BR / Fredrik >> >> -- >> 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-appengine+unsubscr...@googlegroups.com. >> 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
