[Standards-JIG] Re: Stream compression (JEP-138) and notificationoffailure or success (repost from JSF Members)

Peter Saint-Andre stpeter at jabber.org
Wed Jan 11 20:51:34 UTC 2006

How about this?

"If the receiving entity finds the requested method unacceptable or 
unworkable for any other reason, it MUST return a <setup-failed/> error:"


Gaston Dombiak wrote:
> Hey Peter,
> That looks a lot better to me. However, I think that "If the receiving 
> entity cannot establish compression using the requested method for any other 
> reason, it MUST return a <setup-failed/> error:" before example  4 might 
> give the impression that the server should try to establish compression at 
> that point and if something goes bad then a <setup-failed/> error is going 
> to be returned. I would recommend replacing the *establish* word with 
> something else like "accept".
> Thanks,
>   -- Gato
> "Peter Saint-Andre" <stpeter at jabber.org> wrote in message 
> news:43C54B0D.7050609 at jabber.org...
>> Sebastiaan Deckers wrote:
>>> Alright, you guys win. :-)
>> :-)
>> How does this look?
>> http://www.jabber.org/jeps/tmp/jep-0138-1.2.html
>> http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/cvs/jeps/0138/jep-0138.xml?r1=1.17&r2=1.18
>> (I made a few other minor editorial changes at the same time, feel free to 
>> ignore those.)
>> Peter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060111/31e225f2/attachment.bin>

More information about the Standards mailing list