Mercurial > libervia-backend
comparison src/plugins/plugin_misc_groupblog.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 | 2daf7b4c6756 |
| children | 33c8c4973743 |
comparison
equal
deleted
inserted
replaced
| 2143:c3cac21157d4 | 2144:1d3f73e065e1 |
|---|---|
| 63 host.trigger.add("XEP-0277_data2entry", self._data2entryTrigger) | 63 host.trigger.add("XEP-0277_data2entry", self._data2entryTrigger) |
| 64 host.trigger.add("XEP-0277_comments", self._commentsTrigger) | 64 host.trigger.add("XEP-0277_comments", self._commentsTrigger) |
| 65 | 65 |
| 66 ## plugin management methods ## | 66 ## plugin management methods ## |
| 67 | 67 |
| 68 def getHandler(self, profile): | 68 def getHandler(self, client): |
| 69 return GroupBlog_handler() | 69 return GroupBlog_handler() |
| 70 | 70 |
| 71 @defer.inlineCallbacks | 71 @defer.inlineCallbacks |
| 72 def profileConnected(self, profile): | 72 def profileConnected(self, client): |
| 73 client = self.host.getClient(profile) | |
| 74 try: | 73 try: |
| 75 yield self.host.checkFeatures((NS_PUBSUB_GROUPBLOG,), profile=profile) | 74 yield self.host.checkFeatures((NS_PUBSUB_GROUPBLOG,), profile=client.profile) |
| 76 except exceptions.FeatureNotFound: | 75 except exceptions.FeatureNotFound: |
| 77 client.server_groupblog_available = False | 76 client.server_groupblog_available = False |
| 78 log.warning(_(u"Server is not able to manage item-access pubsub, we can't use group blog")) | 77 log.warning(_(u"Server is not able to manage item-access pubsub, we can't use group blog")) |
| 79 else: | 78 else: |
| 80 client.server_groupblog_available = True | 79 client.server_groupblog_available = True |