- From: Miles Fidelman <mfidelman@meetinghouse.net>
- Date: Sat, 01 Jun 2013 17:16:53 -0400
- To: public-fedsocweb@w3.org
Simon Tennant wrote: > On 1 June 2013 20:20, Melvin Carvalho <melvincarvalho@gmail.com > <mailto:melvincarvalho@gmail.com>> wrote: > > > I think XMPP is great as part of an overall solution in the FSW. > And I'm keen that XMPP systems should be able to communicate with > other systems. The JID xmpp:user@host in my view is an excellent > choice of identifer, I can add it to may roster, and there's a > well defined way to send the messages. > > But we need solutions in the HTTP space as well. Facebook for > example have decent solutions in HTTP, email AND XMPP. It's just > a pity it's centralized and proprietary. > > > XMPP: very good at federation and identity / not very good at display > and client apps > HTTP: no native federation and identity / excellent at display and > client apps > > So (and this is how we built buddycloud), use HTTP to get that > information from your home domain via an API, and use XMPP to > transport and share between domains. Exactly! -- In theory, there is no difference between theory and practice. In practice, there is. .... Yogi Berra
Received on Saturday, 1 June 2013 21:17:17 UTC