- It is smaller. While individual pieces of data may be
tiny, the
cumulative amount is significant, and efficiency is crucial.
Why is efficiency crucial when events are being produced at the rate a human
can produce them?
If something
over Jingle *is* desired, I'm a bit uncomfortable with
specifying bespoke binary protocols in XEPs.
The whole point of Jingle applications is to specify the protocol. I'm not
sure where the problem lies here.
Do we have any examples of a XEP specifying a protocol yet? So far usually
we reuse a protocol, such as RTP.
Regarding direct XML streams, CBOR is still more
efficient.
No one is saying CBOR is bad in general, but I think if a new
input-events-over-cbor-stream protocol is needed the XSF is not the place to
specify it.
Additionally, the protocol is based on web APIs, and
CBOR provides a direct
mapping.
Perhaps this could be called out more? If this is indeed a "direct mapping"
to an existing protocol maybe the concerns about it being bespoke are moot.