We have no such plans to announce at this time.  Feel free to make and star
an issue for it.
-- Dan

On Mon, Feb 9, 2009 at 4:43 PM, Onestone <onest...@gmail.com> wrote:

>
> Dan, are there any plans to eventually support client-side BOSH
> (a.k.a. HTTP-binding for XMPP)? Server-side XMPP support is not very
> useful, but client-side BOSH support would be great.
>
> On Feb 9, 7:56 pm, Dan Sanderson <dansander...@google.com> wrote:
> > XMPP support will not take the form of long running processes.  XMPP
> > connections will be maintained by servers that relay incoming messages to
> > the app's XMPP handlers, each of which will execute just like an HTTP
> > request handler.  There will also be an API for sending XMPP messages
> from
> > the app, among other things.
> > -- Dan
> >
> > On Sat, Feb 7, 2009 at 7:24 AM, Roberto Saccon <rsac...@gmail.com>
> wrote:
> >
> > > Uuhh, typo, I mean XMPP, see
> > >http://code.google.com/intl/und/appengine/docs/roadmap.html
> >
> > > On Feb 7, 12:20 pm, Roberto Saccon <rsac...@gmail.com> wrote:
> > > > Now we know it, XMMP comes to appengine. So far, appengine has been
> > > > limited to shortlived-HTTP requests.  What are the educated guesses
> > > > (or somebody who knows it, is allowed to speak out loud here ...),
> > > > will XMMP bring streaming HTTP request with possibly longer lifetime
> > > > than 10 sec to appengine (but also higher cost, like HTTPS), so we
> can
> > > > do long-polling or other serverpush hacks ? Or none of this, it will
> > > > run on the same platform and just normal polling will be
> > > > "encouraged" ?
> >
> > > > Roberto
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to