I agree in the need for multiple subscriptions. I have that in several
usecases.
I would also adress the keep it simple need the xep 323 is very easy to
use and the need for events for small sensors are essential to
prevent extensive polling.
Demanding pubsub and forms notation to the devices
On 10/8/14, 9:59 PM, dricha...@coversant.com wrote:
-Original Message-
From: Standards [mailto:standards-boun...@xmpp.org] On Behalf Of Florian
Zeitz
Sent: Wednesday, October 08, 2014 8:00 PM
To: standards@xmpp.org
Subject: Re: [Standards] draft-ietf-xmpp-websocket-10
On 08.10.2014
Hello all,
Stream compression is insecure, that was shown with CRIME and BREACH and the
situation for XMPP isn't much different [1]. I think we should look at the
easiest way to deprecate XEP-0138 and move to something better.
Using a full flush (in zlib terms) after every stanza would solve the
-Ursprüngliche Nachricht-
Von: Standards [mailto:standards-boun...@xmpp.org] Im Auftrag von
Florian Zeitz
Gesendet: Donnerstag, 9. Oktober 2014 03:00
An: standards@xmpp.org
Betreff: Re: [Standards] draft-ietf-xmpp-websocket-10
On 08.10.2014 20:42, dricha...@coversant.com wrote:
On 10/9/14, 7:59 AM, Thijs Alkemade wrote:
Hello all,
Stream compression is insecure, that was shown with CRIME and BREACH and the
situation for XMPP isn't much different [1]. I think we should look at the
easiest way to deprecate XEP-0138 and move to something better.
Using a full flush (in
On 9 October 2014 15:26, Hund, Johannes johannes.h...@siemens.com wrote:
One point that I do realize now (too late) is that this means it's not
possible to use EXI (XEP-0322) over websocket, right?
It's basically a 1:1 binary representation of the information in an XML
structure/document and
