This is not implemented in CAXL either. Given just about none of the known web-based XMPP libraries implement it, the rationale seems to be moot now.
I think its safe to remove altogether. - m&m Matthew A. Miller < http://goo.gl/LK55L > On Feb 5, 2013, at 6:08 AM, Peter Saint-Andre (psaintan) <[email protected]> wrote: > As I recall this was added to support really ok browsers. > > Sent from mobile, might be terse > > On Feb 5, 2013, at 4:27 AM, "Steffen Larsen" <[email protected]> wrote: > >> True true, >> Ive been looking on some other client implementations as well, and they do >> not implements it as well. So I think it seems sane to remove it. >> >> /Steffen >> >> On Feb 5, 2013, at 12:24 PM, Ashley Ward <[email protected]> wrote: >> >>> We don't use it in emite either. >>> >>> Also clients which do implement it should fall back gracefully to utf-8 >>> anyway. >>> >>> -- >>> Ash >>> >>> On 04/02/2013 21:57, "Stefan Strigler" <[email protected]> wrote: >>> >>>> JSJaC doesn't either. And at least the old implementation of ejabberd's >>>> mod_http_bind didn't as well. >>>> >>>> .Steve >>>> >>>> Am 04.02.2013 um 22:39 schrieb Steffen Larsen <[email protected]>: >>>> >>>>> Just checked strophe, and it does not use it. I'll check some more >>>>> implementations that uses BOSH for transport. Maybe that would give us >>>>> an indication. >>>>> >>>>> /Steffen >>>>> >>>>> On Feb 4, 2013, at 10:06 PM, "Peter Saint-Andre (psaintan)" >>>>> <[email protected]> wrote: >>>>> >>>>>> That sounds sensible. >>>>>> >>>>>> Sent from mobile, might be terse >>>>>> >>>>>> On Feb 4, 2013, at 1:26 PM, "Ashley Ward" <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> It would be great to keep them consistent, but is it worth potentially >>>>>>> breaking implementations? I think the main problem with accept was >>>>>>> that >>>>>>> the example was inconsistent with the text. >>>>>>> >>>>>>> In fact, I very much doubt anyone should be using that option as xmpp >>>>>>> mandates the use of utf-8, and I doubt anyone's using bosh for >>>>>>> anything >>>>>>> other than xmpp. Perhaps we should just look at getting rid of that >>>>>>> attribute? >>>>>>> >>>>>>> -- >>>>>>> Ash >>>>>>> >>>>>>> On 04/02/2013 10:30, "Steffen Larsen" <[email protected]> wrote: >>>>>>> >>>>>>>> Cross-posted from the summit list (sorry making noise). >>>>>>>> Here are my small notes to the BOSH action list (embedded). >>>>>>>> >>>>>>>> >>>>>>>> /Steffen >>>>>>>> >>>>>>>> Begin forwarded message: >>>>>>>> >>>>>>>>> From: "Peter Saint-Andre (psaintan)" <[email protected]> >>>>>>>>> Subject: Re: [Summit] BOSH actions >>>>>>>>> Date: February 2, 2013 10:18:01 PM GMT+01:00 >>>>>>>>> To: XMPP Summit <[email protected]> >>>>>>>>> Cc: Bidirectional Streams Over Synchronous HTTP <[email protected]>, >>>>>>>>> XMPP >>>>>>>>> Summit <[email protected]> >>>>>>>>> Reply-To: XMPP Summit <[email protected]> >>>>>>>>> >>>>>>>>> Maybe it would be better to take the technical discussion to the >>>>>>>>> standards@ list? >>>>>>>>> >>>>>>>>> Sent from mobile, might be terse >>>>>>>>> >>>>>>>>> On Feb 2, 2013, at 4:32 PM, "Steffen Larsen" <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hey, >>>>>>>>>> >>>>>>>>>> Just saw the issue with the accept attribute. How about charset? >>>>>>>>>> It is >>>>>>>>>> currently space separated in the example (and it also says) - but >>>>>>>>>> should we not comma separate that like the accept attribute? >>>>>>>>>> >>>>>>>>>> Its on 7.2 in http://xmpp.org/extensions/xep-0124.html: >>>>>>>>>> charsets='ISO_8859-1 ISO-2022-JP' >>>>>>>>>> -Just my 50 cent >>>>>>>>>> >>>>>>>>>> /Steffen >>>>>>>>>> >>>>>>>>>> On Feb 2, 2013, at 4:18 PM, Winfried Tilanus <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi all, >>>>>>>>>>> >>>>>>>>>>> I updated the BOSH issues page with the results & and who will be >>>>>>>>>>> writing patches. >>>>>>>>>>> http://wiki.xmpp.org:12480/web/BoshIssues >>>>>>>>>>> >>>>>>>>>>> I only forgot who will be writing the patch for the first issue >>>>>>>>>>> (remove >>>>>>>>>>> Pipelining). Plz check if your name pops up at the correct places >>>>>>>>>>> and >>>>>>>>>>> ping me if there are any problems! >>>>>>>>>>> >>>>>>>>>>> happy patch-writing! >>>>>>>>>>> >>>>>>>>>>> Winfried >>
smime.p7s
Description: S/MIME cryptographic signature
