Hi, Also, not having the 'sessionID' parameter in the ACK, makes it difficult to create packet filters that match incoming packets to the right packet receivers. If a need 'sessionID', I would also have to encode into 'id'.
William On 7/18/07, William Voorsluys <[EMAIL PROTECTED]> wrote:
Hello, Yes, we can use 'id' for that purpose, possibly encoding 'seq' into it. I just thought that sending the seq number back to the sender would be a "clean" solution. Thanks. William. On 7/18/07, Mridul Muralidharan <[EMAIL PROTECTED]> wrote: > William Voorsluys wrote: > > Hello, > > > > We're adding flow rate control support for IBB since our application > > makes heavy use of file transfers. > > Since we need to receive ACKs for packets, we're using <iq> for data > > transport, according to XEP-0047. The first problem is that the > > algorithm we're using needs to know the sequence number of the packet > > being acknowledged. > > But, according to the XEP, it is not allowed to include any inner XML > > stanza on the <iq> of type RESULT used as ACK: > > > > <iq from='[EMAIL PROTECTED]/balcony' to='[EMAIL PROTECTED]/orchard' > > type='result' id='ibb1'/> > > > > What would be the best way of including this information in the ACK? > > Should we use <message> + AMP for having that info? > > > > Thank you, > > > > William > > Hi, > > You could encode the sequence number into the 'id' attribute ? > > Regards, > Mridul > -- William Voorsluys williamvoor.googlepages.com
-- William Voorsluys williamvoor.googlepages.com
