That's a loaded question! As though the Servlet API were some sort of malefactor, intentionally and improperly...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
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.
Dig Deeper on API management strategy
Related Q&A from Jason Bloomberg
What are chief criteria for analyzing "enterprise mashups"? Especially in relation to a "mainframe w
What are chief criteria for analyzing "enterprise mashups"? Especially in relation to a "mainframe wrappering" project? Jason Bloomberg has the ...continue reading
Jason Bloomberg answers questions of ESB usage.continue reading
Is it good to discuss elements of EA with business users - for example should one let them know if the group is looking to apply TOGAF or other ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.