Daniel Calviño Sánchez 68cf4ee028 Use generic data channel message instead of nick specific one ... The generic data channel message works fine for receiving, but it could not be used for sending, because the serialization of the payload failed (the generated JsonMapper did not call 'writeFieldName("payload")', apparently because the payload was defined as "Any", so there was no field name set when serializing the payload contents). It is very likely that the nick data channel message, which has an explicit payload type and was used only for sending but not for receiving, was added back in the day just to work around that limitation. However, due to how the JsonMappers are generated if several properties with the same name are defined only the first one will be parsed, and only those with a value will be serialized. This makes possible to define first a generic payload property and then a payload property with an explicit type to have a single data channel message class that can be used both for sending and receiving. As the nick data channel message is now no longer needed it was removed. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>		2022-12-28 11:47:55 +01:00
..
talk	Use generic data channel message instead of nick specific one	2022-12-28 11:47:55 +01:00