Difference between revisions of "DevCon3Agenda"

Jump to navigation Jump to search
660 bytes added ,  19:10, 24 July 2007
Line 4: Line 4:


==XMPP-CORE==
==XMPP-CORE==
* [http://www.xmpp.org/extensions/xep-0198.html XEP-0198: Stanza Acknowledgements]
 
* Mixed child elements in message/presence -- put in order, process in order (PSA nominates Justin to write a best practices doc about this!)
[http://www.xmpp.org/extensions/xep-0198.html XEP-0198: Stanza Acknowledgements]
* Stanza size limitations (specify that stanza-too-big error includes max stanza size, specify IQ interaction for client to set its desired max stanza size)
 
Mixed child elements in message/presence
* Each message stanza is of a single profile.
* Transmission elements don't affect the profile, and these elements need to be noted as transmission elements in whatever document proposes them (e.g. x:delay, AMP).
* Each element is part of some profile.  Unless otherwise stated, every element of a given namespace is in the same profile.
* Unknown elements don't affect the profile.
* Mixing profiles is invalid, except that you may mix the IM profile with any other profile as a fallback means.
* When determining what profile a stanza falls under, consider the IM profile as a last resort.
* need to specify in transmission specs that they are transmission elements
* need to specify in message payload specs that they are in IM profile or some other profile
 
Stanza size limitations
* specify that stanza-too-big error includes max stanza size
* specify IQ interaction for client to set its desired max stanza size


==COMPONENT PROTOCOL==
==COMPONENT PROTOCOL==
81

edits

Navigation menu