celix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Broekhuis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CELIX-217) Adapt discovery_shm to use discovery server
Date Mon, 09 Feb 2015 12:25:34 GMT

    [ https://issues.apache.org/jira/browse/CELIX-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312169#comment-14312169

Alexander Broekhuis commented on CELIX-217:

Already emailed with Bjoern about this, but adding it here for future reference. The update
SHM discovery uses the discovery webserver, and as such is not strictly based on shared memory
anymore. I think we need a solution that does not require any web technology, and that this
discovery should still use shared memory.

I do think it makes sense to use the XML format, and as such I think we should split the current
discovery into a endpoint handling and a separate transport part. Than the endpoint handling
can be reused, and a new transport can be added for SHM. This also makes it possible for different
solutions wrt discovery.

This can leave the basic architecture intact, where the discovery itself is "discovered" through
any other means, and only after this discovery a direct communication is in place for retrieving
the endpoints. But where needed/possible on mechanism can be used for both. I think that for
SHM both solutions are possible.

> Adapt discovery_shm to use discovery server
> -------------------------------------------
>                 Key: CELIX-217
>                 URL: https://issues.apache.org/jira/browse/CELIX-217
>             Project: Celix
>          Issue Type: Improvement
>            Reporter: Bjoern Petri
>            Assignee: Bjoern Petri
> To ease implementation and refactoring, discovery shm should also use discovery shm,
comparable to discovery http and etcd.

This message was sent by Atlassian JIRA

View raw message