-
PEP processor forwards it for processing to PubSub component as only PubSub component is aware of the features that are available currently for particular JID/account. Due to that, it would be hard to embed it in processor extension without exposing PubSub component to the processor (possibly forcing requests on the PubSub repository from the
sess-manthreads).
| Type |
Improvement
|
| Priority |
If you are bored
|
| Assignee | |
| Version |
none
|
| Sprints |
n/a
|
| Customer |
n/a
|
Iterations
Issue Votes (0)
Currently,
ServiceDiscoveryplugin relies on injectingtigase.xmpp.impl.ServiceDiscovery.AccountServiceProvider(only PEP fromtigase-pubsubsupports it) and if it is present it forwards query to the PEP plugin/pubsub for processing.It would be better to make the logic extensible and allow creating multiple provider implementations and call them to add particular features to service discovery and combine the result in one request. It would simplify the processing logic and give us more flexibility.