I agree that UDDI is just a part of the entire webservice framework, but definitely an imporant one.
In your mail, you are trying to distinguish between "SOAPizing" and "Webservizing". I think they are essentially the same. when you look at the definition SOAP itself(HTTP +XML), web is an inherent feature of SOAP. In that sense its natural to "publish" and "locate" SOAP service on the web. One alalogy of UDDI that comes to my mind is that of DNS(Domain Naming service), it enables you to resolve a url name to a IP address. Similary a UDDI service maps a webservice to its deployed location on the web. Also, another advantage of UDDI is automation, when you want to have seamless connectivity from end to end. i.e use UDDI to locate a webservice, then use WSDL to look at the published services and then invoke the desired methods on the service. hope this helps nilesh -----Original Message----- From: soap vamsi [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 10:06 AM To: Harry Mynmann Cc: [EMAIL PROTECTED] Subject: Re: Re: why uddi? yes Harry i agree that UDDI is just a part of the webservices framework.But insignificant??? ,in my opinion web services is leveraging mainly on this capabilty to allow dynamic discovery of service info. I do not contest the need for SOAPizing(if i may call it so) applications,my query therefore was the need webservisize my application. What advantage will i get by doing this?Is it anything other than my being able to publish it in a pulic registry? pl clarify vamsi On Tue, 28 May 2002 Harry Mynmann wrote : >Hi : > >. > >UDDI is more of a registry of services. It is NOT Web Services, >just a small >part - in my opinion, insignificant. Web Services is made of >many >components - the most important being using SOAP as a protocol, >XML over >HTTP. > > > >----- Original Message ----- > From: "soap vamsi" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Sunday, May 26, 2002 10:35 PM >Subject: why uddi? > > > > I am not sure if this is the right place for this query ,I >will > > be grateful though for any information in this direction. > > My query is regarding the services that are likely to become > > webservices and the need for uddi. > > In my opnion there are two senarios where webservies might >find > > place > > 1.b2b. > > 2.b2c. > > Firstly in a b2b senario one business knows the other.Where is >the > > need to dynamically discover the service using uddi? > > In a b2c senario when if the client doesnot know the >business > > service provider the need for uddi is warrnated,but here the > > client(i am referening to an end user) needs to soap aware >and > > soap capable to avail those services.To what extent is this >a > > realistic expectation? > > If i am wrong in my extrapolation regd the likely >webservices, > > what services to become webservices? > > > > I may have been myopic in my opinion formation,pl feel free >to > > make me aware of the possiblities that i have overlooked. > > Thaking you > > vamsi > > > > _________________________________________________________ > > Click below to visit monsterindia.com and review jobs in India >or > > Abroad > > http://monsterindia.rediff.com/jobs > > > > _________________________________________________________ Click below to visit monsterindia.com and review jobs in India or Abroad http://monsterindia.rediff.com/jobs
