[Standards] S5B and proxy connect errors

Peter Saint-Andre stpeter at stpeter.im
Wed Nov 18 21:37:09 UTC 2009

On 11/15/09 1:28 PM, Marcus Lundblad wrote:
> fre 2009-11-13 klockan 15:31 +0900 skrev Peter Saint-Andre:
>> So this is only for problems connecting to the proxy (which perhaps
>> could be checked ahead of time, as Pedro suggests) or also with problems
>> related to activation (as you say, if the hashes don't match or the
>> proxy doesn't like A's credentials)? Do you think we need separate error
>> conditions for those cases? IMHO we can use <proxy-error/> for both.
>> Thus A would send something like the following to B:
>> <iq from='romeo at montague.lit/orchard'
>>     id='hx91j3s6'
>>     to='juliet at capulet.lit/balcony'
>>     type='set'>
>>   <jingle xmlns='urn:xmpp:jingle:1'>
>>           action='transport-info'
>>           initiator='romeo at montague.lit/orchard'
>>           sid='a73sjjvkla37jfea'>
>>     <content creator='initiator' name='stub'>
>>       <transport xmlns='urn:xmpp:jingle:transports:s5b:1'
>>                  sid='vj3hs98y'>
>>         <proxy-error/>
>>       </transport>
>>     </content>
>>   </jingle>
>> </iq>
>> Good catch!
> Yes, using the same error for both seems reasonable (from B's
> perspective it shouldn't really matter what went wrong).

OK. I'll work this into the next version of the spec, because I will
review and update all the Jingle file transfer documents Real Soon Now.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6820 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20091118/a6360547/attachment.bin>

More information about the Standards mailing list