[Standards] XEP-0047 (Flow rate control for IBB)

Alex Wenckus alex at jivesoftware.com
Fri Jul 20 03:58:20 UTC 2007


I can think of a few ways this could be handled gracefully in the context of Smack, other then the way you have proposed. If you would like feel free to contact me off-list so that we can discuss it.


----- Original Message -----
From: "William Voorsluys" <williamvoor at gmail.com>
To: "XMPP Extension Discussion List" <standards at xmpp.org>
Sent: Thursday, July 19, 2007 2:04:25 PM (GMT-0800) America/Los_Angeles
Subject: Re: [Standards] XEP-0047 (Flow rate control for IBB)


> > Justin, what say you?
> I'm against adding redundant information like this into the stanzas.
> Maybe William can explain what he means by "filtering" and how this is
> difficult?

This is really an implementation issue and is more related to parsing.
Suppose I need both 'sid' and 'seq' to be included in the response.
Without child elements I would use an 'id' like "sid001_10". Since the
values I need are not as an XML structure, I need to create a special
"ID parser" that would break the id into pieces and deliver the values
to the application.
This is needed because we want to create Packet Filters in the Smack
library that only match a specific session id. Messages of the
different sessions are delivered to different Objects (the Packet
Listeners or Packet Collectors). If I don't break the 'id' and get
'sid' to use as the argument input, I have to create one Packet
Collector for each message sent, using the full 'id' as the filter
argument, so that the correct sender will receive the message

As I said, this is an implementation issue and we could cope with
using just 'id' for tracking packets, even though it makes the
implementation harder.



More information about the Standards mailing list