RE: jUDDI as UDDI repository

[Andy Cutright <An...@borland.com>]

moving to dev list. 
 
i've just re-read the spec and the defined asynchronous interface is
notify_subscriptionListener. there's no other UDDI compliant method,
that i can find. could be wrong of course:
 
http://uddi.org/pubs/uddi_v3.htm#_Toc53709334
 
cheers,
andy 


  _____  

	From: Jeff Lansing [mailto:jeff@polexis.com] 
	Sent: Thursday, April 08, 2004 9:12 AM
	To: juddi-user@ws.apache.org
	Subject: Re: jUDDI as UDDI repository
	
	
	Yes. There are two sort of ok ways of implementing this, that I
know of; one is really asynchronous and uses communicating web
service/web client pairs, the other is pseudo-asynchronous, and uses
controlled blocking on the server side.
	
	The first method has two interfaces A and B. The server side of
A is the "Service", such as UDDI. The client side of A is the
subscriber. Interface A has a subscribe operation, which allows the
subscriber to register its interests (a "standing query"). Interface B
has a publish operation (which is where the data flows). The client side
of B is notionally part of the "Service", the server side of  B is -- as
Andy says -- provided by the subscriber. The subscriber might need to
use some kind of  IPC (inter-process communication) to keep A-client and
B-service in synch