Re: [Standards] XEP-0322: EXI for constrained processing environments

2015-07-01 Thread Peter Waher
Hello Dave. > On 30 June 2015 at 18:40, Peter Waher < > peter.wa...@clayster.com> wrote: >Thanks for your input. For small devices, that do not wish to (or cannot) >perform a dynamic handshake, there's the concept of quick configurations >(§2.6). With a quick

Re: [Standards] Request HTTP upload slots over XMPP

2015-07-01 Thread Peter Waher
Hello Edwin > So, you're suggesting an in-band transfer mechanism for out-of-band data > transfers? That sounds a bit wasteful to me. XEP-0332 allows the client and server to use different methods based on your requirements and capabilites. It supports both chunked transfer, as well as

Re: [Standards] XEP-0322: EXI for constrained processing environments

2015-07-01 Thread Rick van Rein
Hi Daniel, Thanks for the references; I had indeed missed discussion. I also noted that the Last Call seems to have been closed. > I think you gave yourself the answer in the latter part of your mail > mentioning that with a dedicated port one can start using EXI right-away. > Is this approach

Re: [Standards] XEP-0322: EXI for constrained processing environments

2015-07-01 Thread Rick van Rein
Hi Dave, > It's remarkable how small XML processors can be these days, but in any > case, have you considered how encryption fits into this, or were you > assuming a trusted network? Have not (as is common with XMPP). I can imagine that there would be applications of constrained environments, po

Re: [Standards] Push and headline messages

2015-07-01 Thread Mickaël Rémond
Hello, On 1 Jul 2015, at 11:42, Dave Cridland wrote: On 1 July 2015 at 09:20, Mickaël Rémond wrote: I think it implies that they should not be pushed as well. Otherwise, you may receive a push notification for a message you will never be able to receive if you reconnect. Am I wrong ? Do

Re: [Standards] Push and headline messages

2015-07-01 Thread Dave Cridland
On 1 July 2015 at 09:20, Mickaël Rémond wrote: > Hello, > > XEP-0160 clarify the best practice for offline message and states for > offline messages that headline message should not be stored for offline > delivery: > > headline -- Messages with a 'type' attribute whose value is "headline" >> SH

[Standards] Push and headline messages

2015-07-01 Thread Mickaël Rémond
Hello, XEP-0160 clarify the best practice for offline message and states for offline messages that headline message should not be stored for offline delivery: headline -- Messages with a 'type' attribute whose value is "headline" SHOULD NOT be stored offline, since such messages are usually

Re: [Standards] XEP-0322: EXI for constrained processing environments

2015-07-01 Thread Dave Cridland
On 26 June 2015 at 05:41, Rick van Rein wrote: > I am thinking of constrained processing environments, such as clients on > microcontrollers. These may want to use EXI to avoid having to deal > with the full XML notation, and they would most certainly not be > serviced if they have to go through

Re: [Standards] XEP-0322: EXI for constrained processing environments

2015-07-01 Thread Dave Cridland
On 30 June 2015 at 18:40, Peter Waher wrote: > Thanks for your input. For small devices, that do not wish to (or cannot) > perform a dynamic handshake, there's the concept of quick configurations > (§2.6). With a quick configuration ID, the entire setup is predefined. It > can be defined, either