Re: Controversial: Have SIMPLE reached is goal? Or is it an IETF failure?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/18/12 12:01 PM, Olle E. Johansson wrote:
> 
> 18 okt 2012 kl. 18:43 skrev Paul Kyzivat <[email protected]>:
> 
>> I will observe that some things are, or can be, UI issues or API 
>> issues rather than protocol issues. For better or worse IETF 
>> doesn't do UI and API. So it's important to draw the lines 
>> carefully. Or establish a partnership with another SDO that does 
>> those things, like W3C, as is going on with RTCWEB/WEBRTC.
> 
> Absolutely. But the requirement to be able to integrate with a UI
> may affect the protocol solution.
> 
> XMPP has this problem. The XMPP server is not aware of the
> presence, it just routes stanzas. Without caching stanzas or doing
> something else, it is just not possible to create an API into the
> server and get the presence of a particular JID.

Olle, that statement has no basis in reality. Every XMPP server
implementation on the planet is aware of the presence state for each
Jabber ID under its control.

Peter

- --
Peter Saint-Andre
https://stpeter.im/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCATYoACgkQNL8k5A2w/vzgngCgyUbd8x7gvtopn9dylgdKRpuk
PLAAn398pHliBOEXqLhb2WkvjkIABLzf
=Rtdu
-----END PGP SIGNATURE-----