Is Microsoft SOAP Toolkit a viable option to develop Web services?

Is Microsoft SOAP Toolkit a viable option to develop Web services?

Is Microsoft SOAP Toolkit a viable option to develop Web services? What are the advantages and problems of Microsoft SOAP Toolkit? Is latency the main problem?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Microsoft SOAP Toolkit is most certainly a viable option to develop Web services. I recommend that you use the latest version of the toolkit. MS SOAP Toolkit supports all COM languages on all Windows platforms (Win 95, 98, NT, 2000, XP, CE). (.NET requires installation of the .NET Framework, which is only available for Win 2000, XP, and CE, it it requires that you upgrade to VB.NET and ASP.NET.) I don't view latency as a problem. MS SOAP Toolkit isn't the best performing SOAP implementation on the market, but it's certainly viable.

Your other options for pre-.NET COM languages are pocketSOAP (client only), 4s4c (server only), White Mesa, and IP*Works.


This was first published in October 2002

Back to top