plugin XEP-0353, XEP-0234, jingle: WebRTC data channel signaling implementation: Implement XEP-0343: Signaling WebRTC Data Channels in Jingle. The current version of the XEP (0.3.1) has no implementation and contains some flaws. After discussing this on xsf@, Daniel (from Conversations) mentioned that they had a sprint with Larma (from Dino) to work on another version and provided me with this link: https://gist.github.com/iNPUTmice/6c56f3e948cca517c5fb129016d99e74 . I have used it for my implementation. This implementation reuses work done on Jingle A/V call (notably XEP-0176 and XEP-0167 plugins), with adaptations. When used, XEP-0234 will not handle the file itself as it normally does. This is because WebRTC has several implementations (browser for web interface, GStreamer for others), and file/data must be handled directly by the frontend. This is particularly important for web frontends, as the file is not sent from the backend but from the end-user's browser device. Among the changes, there are: - XEP-0343 implementation. - `file_send` bridge method now use serialised dict as output. - New `BaseTransportHandler.is_usable` method which get content data and returns a boolean (default to `True`) to tell if this transport can actually be used in this context (when we are initiator). Used in webRTC case to see if call data are available. - Support of `application` media type, and everything necessary to handle data channels. - Better confirmation message, with file name, size and description when available. - When file is accepted in preflight, it is specified in following `action_new` signal for actual file transfer. This way, frontend can avoid the display or 2 confirmation messages. - XEP-0166: when not specified, default `content` name is now its index number instead of a UUID. This follows the behaviour of browsers. - XEP-0353: better handling of events such as call taken by another device. - various other updates. rel 441

--- a/libervia/backend/tools/async_trigger.py	Sat Apr 06 12:21:04 2024 +0200
+++ b/libervia/backend/tools/async_trigger.py	Sat Apr 06 12:57:23 2024 +0200
@@ -20,6 +20,8 @@
 """Misc usefull classes"""
 
 from typing import Tuple, Any
+
+from libervia.backend.core.xmpp import SatXMPPEntity
 from . import trigger as sync_trigger
 from . import utils
 from twisted.internet import defer
@@ -27,8 +29,11 @@
 class TriggerManager(sync_trigger.TriggerManager):
     """This is a TriggerManager with an new async_point method"""
 
-    @defer.inlineCallbacks
-    def async_point(self, point_name, *args, **kwargs):
+    async def async_point(
+        self,
+        point_name: str,
+        *args, **kwargs
+    ) -> bool:
         """This put a trigger point with potentially async Deferred
 
         All the triggers for that point will be run
@@ -41,18 +46,18 @@
         @return D(bool): True if the action must be continued, False else
         """
         if point_name not in self.__triggers:
-            defer.returnValue(True)
+            return True
 
         can_cancel = not kwargs.pop('triggers_no_cancel', False)
 
-        for priority, trigger in self.__triggers[point_name]:
+        for __, trigger in self.__triggers[point_name]:
             try:
-                cont = yield utils.as_deferred(trigger, *args, **kwargs)
+                cont = await utils.as_deferred(trigger, *args, **kwargs)
                 if can_cancel and not cont:
-                    defer.returnValue(False)
+                    return False
             except sync_trigger.SkipOtherTriggers:
                 break
-        defer.returnValue(True)
+        return True
 
     async def async_return_point(
         self,