OK, I'll see the bet and raise the ante. Could you explain succinctly why we need a new protocol at all? Why instead aren't we defining WSDL messages for different functions, and then using SOAP bindings and UDDI to solve the problem? regards,
Umm. Because that would be too easy?
I must say I asked my question in response to thinking about how we would go about building applications that would use a NETCONF interface. It would be nice to have a WSDL description we could just feed into a web services toolkit. WSDL is extensible, though, and should allow us to write a BEEP binding (much like we would write a SOAP binding), and then use UDDI. I just didn't want to be the first one to write a BEEP binding for WSDL. I actually sent an e-mail to the chair of the BEEP WG to see if anyone else has done this. Then all we would need is a web services toolkit that supports BEEP. Keeping my fingers crossed...
Keith Allen SBC Technology Resources 9505 Arboretum Blvd. Austin, TX 78759 (512) 372-5741
-----Original Message-----
OK, I'll see the bet and raise the ante. Could you explain succinctly why we need a new protocol at all? Why instead aren't we defining WSDL messages for different functions, and then using SOAP bindings and UDDI to solve the problem? regards,
-----Original Message-----
At 03:09 PM 4/16/2003 -0500, Allen, Keith wrote: This could be discussed by the WG. So far, I have only heard interest in WSDL from one person. If there is enough WG interest in this extra deliverable, then it could be done by the WG at some point. It could also be done separately, outside the WG, as an Informational RFC.
>Keith Allen Andy
>--
-- archive: <http://ops.ietf.org/lists/xmlconf/> |