How do you plan to ensure that SOAP interoperability happens?
Without it, we will be left with a balkanization between MS-oriented engineers building SOAP apps and others building XML-RPC apps. Surely it is in MS's best interests to make SOAP the popular standard, as this should help drive.NET adoption.
There are currently 39 non-compatible SOAP implementations (and growing...) - how will you embrace or reject or integrate those efforts?
Even better is ZoneAlarm (www.zonealarm.com) which is a free-as-in-beer-for-personal-use "firewall" that alerts you whenever a program attempts to initiate or receive connections to the Internet. I've used it since beta, and I was shocked at the number of programs that try to connect... Knowledge is power.
Slashdot Mirror
Did you mean Hushmail?
How do you plan to ensure that SOAP interoperability happens?
.NET adoption.
Without it, we will be left with a balkanization between MS-oriented engineers building SOAP apps and others building XML-RPC apps. Surely it is in MS's best interests to make SOAP the popular standard, as this should help drive
There are currently 39 non-compatible SOAP implementations (and growing...) - how will you embrace or reject or integrate those efforts?
Cheers!
Even better is ZoneAlarm (www.zonealarm.com) which is a free-as-in-beer-for-personal-use "firewall" that alerts you whenever a program attempts to initiate or receive connections to the Internet. I've used it since beta, and I was shocked at the number of programs that try to connect... Knowledge is power.