It wouldn't be difficult to replicate the capabilities of the UDDI protocols using HTTP GET and POST. The API is document oriented with relatively few methods -- they are find, get, and save, (although a unique set of functions has been defined for each type of entity). More to the point, each entry in the registry has a unique URI. So replace the current findxxx and savexxx methods with a generic POST with the appropriate XML document, and replace getxxx with a generic GET, and it works.

Anne

On 6/27/06, Stefan Tilkov <[EMAIL PROTECTED]> wrote:

On Jun 27, 2006, at 2:27 PM, Anne Thomas Manes wrote:

> Realistically, though, WS-MEX should be designed as an HTTP GET
> operation rather than a SOAP invocation.

Hear, hear ... next thing you'll know you will suggest to re-invent
UDDI in terms of RESTful HTTP :-)


Stefan
--
Stefan Tilkov, http://www.innoq.com/blog/st/


__._,_.___


SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to