Mercurial > libervia-backend
comparison src/plugins/plugin_xep_0184.py @ 2144:1d3f73e065e1
core, jp: component handling + client handling refactoring:
- SàT can now handle components
- plugin have now a "modes" key in PLUGIN_INFO where they declare if they can be used with clients and or components. They default to be client only.
- components are really similar to clients, but with some changes in behaviour:
* component has "entry point", which is a special plugin with a componentStart method, which is called just after component is connected
* trigger end with a different suffixes (e.g. profileConnected vs profileConnectedComponent), so a plugin which manage both clients and components can have different workflow
* for clients, only triggers of plugins handling client mode are launched
* for components, only triggers of plugins needed in dependencies are launched. They all must handle component mode.
* component have a sendHistory attribute (False by default) which can be set to True to allow saving sent messages into history
* for convenience, "client" is still used in method even if it can now be a component
* a new "component" boolean attribute tells if we have a component or a client
* components have to add themselve Message protocol
* roster and presence protocols are not added for components
* component default port is 5347 (which is Prosody's default port)
- asyncCreateProfile has been renamed for profileCreate, both to follow new naming convention and to prepare the transition to fully asynchronous bridge
- createProfile has a new "component" attribute. When used to create a component, it must be set to a component entry point
- jp: added --component argument to profile/create
- disconnect bridge method is now asynchronous, this way frontends can know when disconnection is finished
- new PI_* constants for PLUGIN_INFO values (not used everywhere yet)
- client/component connection workflow has been moved to their classes instead of being a host methods
- host.messageSend is now client.sendMessage, and former client.sendMessage is now client.sendMessageData.
- identities are now handled in client.identities list, so it can be updated dynamically by plugins (in the future, frontends should be able to update them too through bridge)
- profileConnecting* profileConnected* profileDisconnected* and getHandler now all use client instead of profile
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Sun, 12 Feb 2017 17:55:43 +0100 |
| parents | f79935f41125 |
| children | 33c8c4973743 |
comparison
equal
deleted
inserted
replaced
| 2143:c3cac21157d4 | 2144:1d3f73e065e1 |
|---|---|
| 90 self._dictRequest = dict() | 90 self._dictRequest = dict() |
| 91 | 91 |
| 92 # parameter value is retrieved before each use | 92 # parameter value is retrieved before each use |
| 93 host.memory.updateParams(self.params) | 93 host.memory.updateParams(self.params) |
| 94 | 94 |
| 95 host.trigger.add("messageSend", self.messageSendTrigger) | 95 host.trigger.add("sendMessage", self.sendMessageTrigger) |
| 96 host.bridge.addSignal("messageState", ".plugin", signature='sss') # message_uid, status, profile | 96 host.bridge.addSignal("messageState", ".plugin", signature='sss') # message_uid, status, profile |
| 97 | 97 |
| 98 def getHandler(self, profile): | 98 def getHandler(self, client): |
| 99 return XEP_0184_handler(self, profile) | 99 return XEP_0184_handler(self, client.profile) |
| 100 | 100 |
| 101 def messageSendTrigger(self, client, mess_data, pre_xml_treatments, post_xml_treatments): | 101 def sendMessageTrigger(self, client, mess_data, pre_xml_treatments, post_xml_treatments): |
| 102 """Install SendMessage command hook """ | 102 """Install SendMessage command hook """ |
| 103 def treatment(mess_data): | 103 def treatment(mess_data): |
| 104 message = mess_data['xml'] | 104 message = mess_data['xml'] |
| 105 message_type = message.getAttribute("type") | 105 message_type = message.getAttribute("type") |
| 106 | 106 |