[
https://issues.apache.org/jira/browse/CELIX-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001324#comment-16001324
]
Pepijn Noltes commented on CELIX-407:
-------------------------------------
[~rlenferink] As discussed per mail, I prefer that the pubsubadmins will be
created per serialiser service. This means that the pubsubadmin do not get more
complex because of the serrializer, because for the lifespan of the admins
there are considered constant. The activators for the admins should of course
then arrange that new admins are created when serialisers become available and
admins are removed when serializer are removed.
Also the discovery properties for publishers (or subscribers) should be
extended with the serializers info and the match functions should take this
into account.
Lastly, It would also be nice to have a distributed test setup using the
add_runtime commands, so that also the pubsub admin has a decent code coverage.
> Extract pubsub_serializer from pubsub_admin
> -------------------------------------------
>
> Key: CELIX-407
> URL: https://issues.apache.org/jira/browse/CELIX-407
> Project: Celix
> Issue Type: Improvement
> Reporter: Roy Lenferink
> Fix For: next
>
>
> At the moment, the pubsub_admin is responsible for both communication and
> serialization. It would be better to extract the serializer from the
> pubsub_admin.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
