The Servlet API and RESTful development

The Servlet API and RESTful development

Do you agree with Restlet proponents that the Servlet API improperly inhibits RESTful development?

    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.

That's a loaded question! As though the Servlet API were some sort of malefactor, intentionally and improperly inhibiting the powers of righteousness!

Let's calm down, people. Remember that Servlets have been with us for over a decade, so no one knew when the notion of a Servlet was fleshed out what we'd want to do with them now. So for example, the fact that the Servlet API assumes one thread per request is now essentially an obsolete notion. There's nothing "improper" going on -- more a case of new tools solving new problems where old tools cannot.

This was first published in July 2008

Back to top