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='[email protected]/orchard' > id='hx91j3s6' > to='[email protected]/balcony' > type='set'> > <jingle xmlns='urn:xmpp:jingle:1'> > action='transport-info' > initiator='[email protected]/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). //Marcus > /psa
