This message is designed to allow us to send an arbitrary JSON payload over XMPP. This is perhaps counterintuitive, but the reasoning is that we plan to move away from XMPP in the future (to JSON over HTTP) so we're leaving the XMPP transport but defining the new messages now.
I made the JsonPacketExtension separate because I think we'll get re-use out of it (Jibri already takes some JSON data and it would be nice to move over to this). I don't know that it's best done as a PacketExtension, though. I did run into some awkwardness around it not having a namespace (it didn't feel like one made sense for it) since extensions on an IQ require lookup via a namespace (I had to add a helper function to work around this)--so suggestions are welcome.
This message is designed to allow us to send an arbitrary JSON payload over XMPP. This is perhaps counterintuitive, but the reasoning is that we plan to move away from XMPP in the future (to JSON over HTTP) so we're leaving the XMPP transport but defining the new messages now.
I made the
JsonPacketExtension
separate because I think we'll get re-use out of it (Jibri already takes some JSON data and it would be nice to move over to this). I don't know that it's best done as a PacketExtension, though. I did run into some awkwardness around it not having a namespace (it didn't feel like one made sense for it) since extensions on anIQ
require lookup via a namespace (I had to add a helper function to work around this)--so suggestions are welcome.