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

["ASF subversion and git services (JIRA)" <ju...@ws.apache.org>]

    [ https://issues.apache.org/jira/browse/JUDDI-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921820#comment-13921820 ] 

ASF subversion and git services commented on JUDDI-648:
-------------------------------------------------------

Commit 215438e4945b0353adcc397803f4f4cf0e0ec603 in juddi's branch refs/heads/master from [~spyhunter99]
[ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=215438e ]

JUDDI-648 adding skeleton project
JUDDI-197 merging code from 3.3 into trunk
JUDDI-241 merging code from 3.3 into trunk
JUDDI-198 merging code from 3.3 into trunk


> 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)