Re: [Standards] BOSH and legacy auth - do we have to be backwards compatible?

2013-03-04 Thread Stefan Strigler
This again leads me back to the question whether we should change SHOULD to MUST within this paragraph: If no stream:features/ element is included in the connection manager's session creation response, then the client SHOULD send empty request elements until it receives a response

Re: [Standards] BOSH and legacy auth - do we have to be backwards compatible?

2013-02-15 Thread Winfried Tilanus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/08/2013 06:28 PM, Peter Saint-Andre wrote: Hi, I think we can remove the XEP-0078 references. It has been obsolete since 2008. Steve, there seem to be no objections. Do you write a patch for it? Winfried -BEGIN PGP SIGNATURE-

Re: [Standards] BOSH and legacy auth - do we have to be backwards compatible?

2013-02-15 Thread Stefan Strigler
OK! Am 15.02.2013 um 13:14 schrieb Winfried Tilanus winfr...@tilanus.com: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/08/2013 06:28 PM, Peter Saint-Andre wrote: Hi, I think we can remove the XEP-0078 references. It has been obsolete since 2008. Steve, there seem to be no

Re: [Standards] BOSH and legacy auth

2013-02-08 Thread Stefan Strigler
Matt, in short words: On 07.02.2013, at 13:54, Matthew Miller linuxw...@outer-planes.net wrote: If I recall correctly, this issue is about what to do when, after authentication, the client sends a restart=true, but the server does not support that (since there is no way to discover the

Re: [Standards] BOSH and legacy auth - do we have to be backwards compatible?

2013-02-08 Thread Winfried Tilanus
On 02/07/2013 01:50 PM, Stefan Strigler wrote: Hi, Stream features are only provided by non legacy servers which might accept legacy auth for backwards compatibility with legacy clients. Legacy servers don't know about stream features. I have been rereading XEP-0078 on this, and you are

Re: [Standards] BOSH and legacy auth - do we have to be backwards compatible?

2013-02-08 Thread Peter Saint-Andre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/8/13 2:37 AM, Winfried Tilanus wrote: On 02/07/2013 01:50 PM, Stefan Strigler wrote: Hi, Stream features are only provided by non legacy servers which might accept legacy auth for backwards compatibility with legacy clients. Legacy

Re: [Standards] BOSH and legacy auth

2013-02-07 Thread Winfried Tilanus
On 02/06/2013 05:05 PM, Stefan Strigler wrote: Hi! regarding the issue listed at http://wiki.xmpp.org/web/BoshIssues#Stream_Creation:_missing_.3Cstream:features.2F.3E I'd propose sth the lines of %== If no stream:features/ element is included in the connection manager's

Re: [Standards] BOSH and legacy auth

2013-02-07 Thread Stefan Strigler
Hi, On 07.02.2013, at 13:12, Winfried Tilanus winfr...@tilanus.com wrote: On 02/06/2013 05:05 PM, Stefan Strigler wrote: regarding the issue listed at http://wiki.xmpp.org/web/BoshIssues#Stream_Creation:_missing_.3Cstream:features.2F.3E Is it correct you are addressing an issue that

Re: [Standards] BOSH and legacy auth

2013-02-07 Thread Matthew Miller
If I recall correctly, this issue is about what to do when, after authentication, the client sends a restart=true, but the server does not support that (since there is no way to discover the server's version of support for XEP-0206). - mm {mobile} On Feb 7, 2013 5:50 AM, Stefan Strigler

[Standards] BOSH and legacy auth

2013-02-06 Thread Stefan Strigler
Hi folks, regarding the issue listed at http://wiki.xmpp.org/web/BoshIssues#Stream_Creation:_missing_.3Cstream:features.2F.3E I'd propose sth the lines of %== If no stream:features/ element is included in the connection manager's session creation response, then the client SHOULD