You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Alex O'Ree (JIRA)" <ju...@ws.apache.org> on 2014/03/03 18:43:20 UTC

[jira] [Updated] (JUDDI-648) Dynamic Runtime registry and UDDI endpoint multicast discovery

     [ https://issues.apache.org/jira/browse/JUDDI-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex O'Ree updated JUDDI-648:
-----------------------------

    Description: 
two concepts
1) Enable juddi-clients to discover the endpoint for UDDI services without knowning their URLs a priori. This reduces the amount of configuration needed to perform lookups. Possible solutions: jgroups, WS-Discovery, mDNS, UPnP

2) Runtime registry - juddi clients can operate with or without access to uddi services using some solution of IP multicast (jgroups, ,Ws-discovery). This runtime registry can then discover other other instances of juddi-client as well as an adapter for service providers

  was:
two concepts
1) Enable juddi-clients to discover the endpoint for UDDI services without knowning their URLs a priori. This reduces the amount of configuration needed to perform lookups. Possible solutions: jgroups, WS-Discovery, mDNS, UPnP

2) Runtime registry - juddi clients can operate with or without access to uddi services using some solution of IP multicast (jgroups, ,Ws-discovery). This runtime registry can then discover other both other instances of juddi-client as well as an adapter for service providers


> Dynamic Runtime registry and UDDI endpoint multicast discovery
> --------------------------------------------------------------
>
>                 Key: JUDDI-648
>                 URL: https://issues.apache.org/jira/browse/JUDDI-648
>             Project: jUDDI
>          Issue Type: New Feature
>          Components: core, juddi-client
>            Reporter: Alex O'Ree
>            Assignee: Kurt T Stam
>             Fix For: 3.3
>
>
> two concepts
> 1) Enable juddi-clients to discover the endpoint for UDDI services without knowning their URLs a priori. This reduces the amount of configuration needed to perform lookups. Possible solutions: jgroups, WS-Discovery, mDNS, UPnP
> 2) Runtime registry - juddi clients can operate with or without access to uddi services using some solution of IP multicast (jgroups, ,Ws-discovery). This runtime registry can then discover other other instances of juddi-client as well as an adapter for service providers



--
This message was sent by Atlassian JIRA
(v6.2#6252)