|
My gut reaction to questions such as this is, "Does it work? If so, does it really matter whether LDAP or UDDI is used behind the scenes?" first and foremost, you need to understand how the registry/repository is being used. If it's used for design-time browsing of available services, the UDDI/LDAP question really doesn't matter. No user is going to want to enter LDAP search filters or a UDDI inquiry messages. They'll want a google like interface for finding services- enter some keywords and see what matches. Now if you're talking the run-time use of a registry/repository with system-to-system interaction, rather than user-to-system interaction, now it actually becomes an important decision. I'll presume that run-time binding of WSDL is important in this case, so it doesn't turn into a debate of whether run-time lookups should be used or not. This becomes a typical integration scenario. You've got two registry options, so now you need to look at the consumer-side stack and see what it supports. If it support both, which is going to be more work for the team developing the consumer? What's the likelihood of a change in development platform for the consumer to where support for UDDI vs. LDAP on other platforms is important? My guess is that UDDI is going to be less work, however, I've never sat down and tried to write that code myself, so I can't say for sure. Unfortunately, the technology industry likes to create new protocols rather than layering some constraints on a general purpose protocol. -tb On Oct 8, 2006, at 8:23 PM, Naren Chawla wrote:
SPONSORED LINKS
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___ |
- Re: [service-orientated-architecture] Re: Ke... Keith Harrison-Broninski
- Re: [service-orientated-architecture] Re... Steve Jones
- Re: [service-orientated-architecture... Keith Harrison-Broninski
- Re: [service-orientated-architec... Steve Jones
- Re: [service-orientated-arc... Ashley at Metamaxim
- Re: [service-orientated... Steve Jones
- Re: [service-orientated... Ashley at Metamaxim
- [service-orientated-arc... Naren Chawla
- Re: [service-orientated... Steve Jones
- Re: [service-orientated... Anne Thomas Manes
- Re: [service-orientated... Todd Biske
- Re: [service-orientated... Gregg Wonderly
- Re: [service-orientated... Todd Biske
- [service-orientated-architecture] An... Keith Harrison-Broninski
- Re: [service-orientated-architec... Hitoshi Ozawa
- RE: [service-orientated-architecture] Re... Guy Crets
- Re: [service-orientated-architecture] Re... Jan Algermissen
- Re: [service-orientated-architecture... Dan Creswell
- Re: [service-orientated-architecture... Keith Harrison-Broninski
- [service-orientated-architecture... Gervas Douglas
- Re: [service-orientated-architecture] Re: Keith o... Eric Newcomer
