[Standards-JIG] proto-JEP: Smart Presence Distribution
Carlo v. Loesch
CvL at mail.symlynX.com
Thu May 25 15:45:19 UTC 2006
Joe Hildebrand said:
| I assume the intent is for this to be widely implemented.
| As such, you might want to take into consideration the architecture
| of some of the existing XMPP servers, which have their S2S components
| decoupled from the piece that does presence management. The presence
| management pieces don't tend to have visibility into the TCP-
| connectedness of the S2S links. In fact, you might have multiple,
| parallel connections, through multiple different physical paths,
| between two domains.
The proto-JEP is designed in a classic internet protocol fashion:
define what happens if everything is fine, then define what to do
if something breaks.
All it needs to be able to operate that way is that the exception
of a 'Transmission Error', as defined in the proto-JEP, may be
forwarded to the involved protocol applications, when they need it.
TCP isn't failsafe, so the application needs to know when something
never made it somewhere.
| I also agree that disco is the way to find out support for this.
Ack. Ack also to Matthias. disco is in. Thanks for the feedback.
| As well, what happens if a user changes a privacy rule in the middle
| of a session?
There are two ways to go about this, the simple way is to 'Reset'
the list for all recipients, then do a new fan-out using the new
recipients. The elaborate way is to look at the changes in detail,
and only 'Update' the involved servers. Both operations are
described in the List Use Cases.
More information about the Standards