Is there any reason they make this decision? Best Regards Leslie From: iot-bounces@xmpp.org [mailto:iot-bounces@xmpp.org] On Behalf Of Ashley Roach Sent: Friday, May 17, 2013 12:40 AM To: XMPP in the Internet of Things Subject: Re: [IOT] google abandoning XMPP? So, that sentiment is expressed in this article: http://www.theverge.com/2013/5/15/4318830/inside-hangouts-googles-big-fix-fo... Talk, for example, was built to help enterprise users communicate better, Singhal says. "The notion of creating something that's social and that's always available wasn't the same charter as we set out with when we created Talk." With Hangouts, Singhal says Google had to make the difficult decision to drop the very "open" XMPP standard that it helped pioneer. Given that my XMPP session to gtalk still works, they clearly haven't abandoned the protocol entirely. My guess is that they changed the backend implementation away from a "pure" XMPP infrastructure (maybe shifted to a different pub sub technology), and provide c2s XMPP "gateway" or the like for compatibility sake. On May 16, 2013, at 10:00 AM, Sebastián Odena <sebodena@gmail.com<mailto:sebodena@gmail.com>> wrote: Does somebody have any news about google abandoning XMPP protocol? _______________________________________________ IOT mailing list IOT@xmpp.org<mailto:IOT@xmpp.org> http://mail.jabber.org/mailman/listinfo/iot

I'll respond, in a way that does pertain to IoT… Google has specifically supported XMPP (by way of Gtalk) in AppEngine: https://developers.google.com/appengine/docs/python/xmpp/overview. I've used this feature myelf to allow an IoT HAN gateway to communicate with AppEngine acting as the datastore & UI: http://blog.thomnichols.org/2013/02/home-automation-with-remohtus So given that Google has an XMPP-specific API built into AppEngine, I do not think they will wholesale abandon XMPP. It would mean deprecating features in AppEngine, which I think would be very bad PR for their PaaS. -Thom From: Ashley Roach <aroach@gmail.com<mailto:aroach@gmail.com>> Reply-To: XMPP in the Internet of Things <iot@xmpp.org<mailto:iot@xmpp.org>> Date: Thursday, May 16, 2013 12:40 PM To: XMPP in the Internet of Things <iot@xmpp.org<mailto:iot@xmpp.org>> Subject: Re: [IOT] google abandoning XMPP? So, that sentiment is expressed in this article: http://www.theverge.com/2013/5/15/4318830/inside-hangouts-googles-big-fix-fo... Talk, for example, was built to help enterprise users communicate better, Singhal says. "The notion of creating something that’s social and that’s always available wasn’t the same charter as we set out with when we created Talk." With Hangouts, Singhal says Google had to make the difficult decision to drop the very "open" XMPP standard that it helped pioneer. Given that my XMPP session to gtalk still works, they clearly haven't abandoned the protocol entirely. My guess is that they changed the backend implementation away from a "pure" XMPP infrastructure (maybe shifted to a different pub sub technology), and provide c2s XMPP "gateway" or the like for compatibility sake. On May 16, 2013, at 10:00 AM, Sebastián Odena <sebodena@gmail.com<mailto:sebodena@gmail.com>> wrote: Does somebody have any news about google abandoning XMPP protocol? _______________________________________________ IOT mailing list IOT@xmpp.org<mailto:IOT@xmpp.org> http://mail.jabber.org/mailman/listinfo/iot This email and any information disclosed in connection herewith, whether written or oral, is the property of EnerNOC, Inc. and is intended only for the person or entity to which it is addressed. This email may contain information that is privileged, confidential or otherwise protected from disclosure. Distributing or copying any information contained in this email to anyone other than the intended recipient is strictly prohibited.