Roadmap update and XMMP
12 views
Skip to first unread message
Roberto Saccon
Feb 7, 2009, 10:20:27 AM2/7/09
to Google App Engine
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
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
Roberto Saccon
Feb 7, 2009, 10:24:23 AM2/7/09
to Google App Engine
Dan Sanderson
Feb 9, 2009, 12:56:39 PM2/9/09
to google-a...@googlegroups.com
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
Roberto Saccon
Feb 9, 2009, 2:21:46 PM2/9/09
to Google App Engine
thanks for the info. So this seems more to be targeted to real IM
clients than something like BOSH over HTTP for in-browser XMPP.
On Feb 9, 2: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
>
clients than something like BOSH over HTTP for in-browser XMPP.
On Feb 9, 2: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
>
P. Petrov
Feb 9, 2009, 7:43:01 PM2/9/09
to Google App Engine
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
>
(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
>
Dan Sanderson
Feb 9, 2009, 9:55:34 PM2/9/09
to google-a...@googlegroups.com
We have no such plans to announce at this time. Feel free to make and star an issue for it.
-- Dan
Reply all
Reply to author
Forward
0 new messages