15 May
2024
15 May
'24
5:48 p.m.
Hi,
I also am not sure why to do this custom-CBOR-via-Jingle approach.
- I don't see a good reason to use CBOR instead of JSON or XML. We're
just adding another object encoding scheme to the protocol suite
without any obvious reason.
- If we define a protocol for remote control, I would prefer this to be
a <message>-based protocol that can be used either using a traditional
XMPP connection or via XEP-0247 Jingle XML Streams.
- Rather than defining our own protocol for remote control and using
traditional video conferencing tech for screen content transfer, I'd
prefer to reuse something like the RFB protocol (RFC 6143), aka. only
create a spec to define how to use RFB via Jingle.
Marvin
On Tue, 2024-05-14 at 21:08 -0500, Stephen Paul Weber wrote:
I'm unclear on the benefits of this CBOR-over-Jingle approach vs a
XML-based
<message>-based approach? Unlike audio/video this data is tiny and
does not
benefit nearly as much from direct transmission or binary packing.
If something over Jingle *is* desired, I'm a bit uncomfortable with
specifying bespoke binary protocols in XEPs. Jingle can of course be
used to
send any data of any protocol and so any existing or future remote-
control
protocol can be used over Jingle. Do we really need something XMPP-
specific
for this purpose?