US 2006/0150200 A1 · Interface infrastructure for creating and interacting with web services

Interface infrastructure for creating and interacting with web services

AssigneeMicrosoft Corporation

InventorsShy Cohen, Geary Eppley, Douglas Purdy, James Johnson, Stephen Millet, Stephen Swartz, Vijay Gajjala, Aaron Stern, Alexander DeJarnatt, Alfred Lee, Anand Rjagopalan, Anastasios Kasiolas, Chaitanya Upadhyay, Christopher Kaler, Craig Critchley, David Levin, David Driver, David Wortendyke, Douglas Walter, Elliot Waingold, Erik Christensen, Erin Honeycutt, Eugene Shvets, Evgeny Osovetsky, Giovanni Della-Libera, Jesus Ruiz-Scougall, John Doty, Jonathan Wheeler, Kapil Gupta, Kenneth Wolf, Krishnan Srinivasan, Lance Olson, Matthew Tavis, Mauro Ottaviani, Max Feingold, Michael Coulson, Michael Marucheck, Michael Vernal, Michael Dice, Mohamed-Hany Ramadan, Mohammad Makarechian, Natasha Jethanandani, Richard Dievendorff, Richard Hill, Ryan Sturgell, Saurab Nog, Scott Seely, Serge Sverdlov, Siddhartha Puri, Sowmyanarayanan Srinivasan, Stefan Batres, Stefan Pharies, Tirunelveli Vishwanath, Tomasz Janczuk, Uday Hegde, Umesh Madan, Vaithialingam Balayogan, Vipul Modi, Yaniv Pessach, Yasser Shohoud

Life of this patent

Estimating the term…

Abstract

A web services namespace pertains to an infrastructure for enabling creation of a wide variety of applications. The infrastructure provides a foundation for building message-based applications of various scale and complexity. The infrastructure or framework provides APIs for basic messaging, secure messaging, reliable messaging and transacted messaging. In some embodiments, the associated APIs are factored into a hierarchy of namespaces in a manner that balances utility, usability, extensibility and versionability.

Claims28

Dependent claims

One or more computer-readable media having thereon the following:

a first plurality of web services APIs, each of which being for writing a distributed, message-passing application, wherein each of the first plurality of web services APIs are represented with a first common namespace prefix for logical grouping of the plurality of web services;
and
a second plurality of web services APIs, each of which being for writing a distributed message-passing application and having certain common characteristics that are not present in all of the first plurality of web services APIs, wherein each of the second plurality of web services APIs are represented having both the first common namespace prefix and a second common namespace prefix that is a sub-namespace of the first common namespace prefix.

Dependencies are inferred from the claim text.