On Sep 5, 1:40 pm, David Symonds <[email protected]> wrote:
> On Sat, Sep 5, 2009 at 7:12 PM, medecau<[email protected]> wrote:
> > Having said that I believe that 50ms per incoming message is too much.
> > I would assume it takes Google less than 50ms to process an XMPP
> > message and deliver it to an app.
>
> There's a lot of work required to bridge two protocols, and an XMPP
> message has to traverse that bridge as well as be processed by both
> sides. Wall time is not the same as CPU time.
>
> Dave.
I understand there might be some work to bridge between XMPP and a GAE
instance but splashing every request with a 50ms overhead seems too
much for me.
XMPP's 50ms are CPU time and my observation is made based only on CPU
time (including APIs CPU use), never total time of request.
Also I made this post because XMPP was just release and I felt the
need to express my opinion on this matter, I never expected XMPP API
to be made available without going through the lab.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
