I'm not watching these particular efforts, but I am somewhat familiar with Web Services and SOAP - the latter being an XML'ized DCOM or CORBA.
These technologies are ideal for gluing together disparate loosely coupled - intra or extra enterprise - applications on heterogeneous platforms. (See: I can string together multiple polysyllabic technical words!) I'm pretty much settling on SOAP for my own products and technologies - where I control both sides: servers and clients. More ambitious coordinated inter-company interoperability efforts (like, maybe, NEHEN) might also make use of Web Services. But I'm guessing SOAP and Web services are not particularly well-suited for our purposes. They presuppose an HTTP based communications infrastructure (though SOAP claims it can be used with other bindings), which we can't assume - because we have all those "disenfranchised" doctors out there with just an e-mail account! Thanks for the links - I'm sure they'll come in handy for my own stuff. William J. Kammerer Novannet, LLC. +1 (614) 487-0320 ----- Original Message ----- From: "Ronald Bowron" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, 14 February, 2002 01:30 PM Subject: Re: auto-discovery of the "return path" (In the Kepa-DNSmodel) Kepa or William, Are either of you watching or aware of Microsofts efforts with regard to SOAP, DIME, WS Referal and WS Routing? Do you see these efforts impacting this group? http://msdn.microsoft.com/library/en-us/dn_voices_webservice/html/servic e01152002.asp http://msdn.microsoft.com/library/en-us/dnglobspec/html/ws-referral.asp http://msdn.microsoft.com/library/en-us/dnglobspec/html/ws-routing.asp Regards, RB
