my guess is that the same service will have multiple entries (one public
and one private) much how dns works today for web servers. this only
solves the issue of allowing external entities to locate a shared
service, not allowing internal clients access to both communities
(unless i am mistaken about the lack of passthourgh queries: search
local then remote, as is the case with dns)
b
On Thu, 2002-04-04 at 19:51, Jeff Broberg wrote:
> I was just trying to find a way so that the model works the same in both an
> intranet where the corporation maintains its own uddi registries, and where
> it potentially exposes some of its services to external ones.
