| US 7,512,957 B2 | ||
| Interface infrastructure for creating and interacting with web services | ||
| Shy Cohen, Bellevue, Wash. (US); Geary L. Eppley, Carnation, Wash. (US); Douglas M. Purdy, Bellevue, Wash. (US); James E. Johnson, Bellevue, Wash. (US); Stephen J. Millet, Edmonds, Wash. (US); Stephen T. Swartz, Seattle, Wash. (US); Vijay K. Gajjala, Sammamish, Wash. (US); Aaron Abraham Stern, Bellevue, Wash. (US); Alexander Martin DeJarnatt, Seattle, Wash. (US); Alfred M. Lee, IV, Seattle, Wash. (US); Anand Rjagopalan, Sammamish, Wash. (US); Anastasios Kasiolas, San Mateo, Calif. (US); Chaitanya D. Upadhyay, Kirkland, Wash. (US); Christopher G. Kaler, Sammamish, Wash. (US); Craig Andrew Critchley, Fall City, Wash. (US); David Edwin Levin, Redmond, Wash. (US); David Owen Driver, Seattle, Wash. (US); David Wortendyke, Seattle, Wash. (US); Douglas A. Walter, Issaquah, Wash. (US); Elliot Lee Waingold, Seattle, Wash. (US); Erik Bo Christensen, Seattle, Wash. (US); Erin P. Honeycutt, Redmond, Wash. (US); Eugene Shvets, Seattle, Wash. (US); Evgeny Osovetsky, Bellevue, Wash. (US); Giovanni M. Della-Libera, Seattle, Wash. (US); Jesus Ruiz-Scougall, Sammamish, Wash. (US); John David Doty, Seattle, Wash. (US); Jonathan T. Wheeler, Bothell, Wash. (US); Kapil Gupta, Redmond, Wash. (US); Kenneth David Wolf, Seattle, Wash. (US); Krishnan Srinivasan, Kirkland, Wash. (US); Lance E. Olson, Sammamish, Wash. (US); Matthew Thomas Tavis, Seattle, Wash. (US); Mauro Ottaviani, Mercer Island, Wash. (US); Max Attar Feingold, Bellevue, Wash. (US); Michael James Coulson, Clyde Hill, Wash. (US); Michael Jon Marucheck, Bellevue, Wash. (US); Michael Steven Vernal, Seattle, Wash. (US); Michael Thomas Dice, Redmond, Wash. (US); Mohamed-Hany Essam Ramadan, Redmond, Wash. (US); Mohammad Makarechian, Seattle, Wash. (US); Natasha Harish Jethanandani, Seattle, Wash. (US); Richard Dievendorff, Bellevue, Wash. (US); Richard Douglas Hill, Kirkland, Wash. (US); Ryan Thomas Sturgell, Seattle, Wash. (US); Saurab Nog, Sammamish, Wash. (US); Scott Christopher Seely, Bellevue, Wash. (US); Serge Sverdlov, Bellevue, Wash. (US); Siddhartha Puri, Sammamish, Wash. (US); Sowmyanarayanan K. Srinivasan, Redmond, Wash. (US); Stefan Batres, Sammamish, Wash. (US); Stefan Harrington Pharies, Seattle, Wash. (US); Tirunelveli Vishwanath, Redmond, Wash. (US); Tomasz Janczuk, Redmond, Wash. (US); Uday S. Hegde, Bellevue, Wash. (US); Umesh Madan, Bellevue, Wash. (US); Vaithialingam B. Balayogan, Bellevue, Wash. (US); Vipul Arunkant Modi, Redmond, Wash. (US); Yaniv Pessach, Redmond, Wash. (US); and Yasser Shohoud, Sammamish, Wash. (US) | ||
| Assigned to Microsoft Corporation, Redmond, Wash. (US) | ||
| Filed on Dec. 03, 2004, as Appl. No. 11/3,307. | ||
| Prior Publication US 2006/0150200 A1, Jul. 06, 2006 | ||
| Int. Cl. G06F 3/00 (2006.01) | ||
| U.S. Cl. 719—328 | 23 Claims |
| 1. One or more computer-readable storage media having stored thereon a plurality of application programming interface (APIs),
the APIs executable by a computer processor, the plurality of APIs comprising:
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 corresponding with a
System.ServiceModel namespace for logical grouping of the plurality of web services, wherein the System.ServiceModel namespace
includes the following classes:
EndpointAddress which represents the definition of the address of a web service;
IChannelFactory which represents the base interface for actively creating channels;
IListenerFactory which represent the base interface for listening at a network address; and
Message which comprises the container within which all data exchanged between web services is encapsulated;
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; and
a third 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 or second plurality of web services APIs, wherein
each of the third plurality of web services APIs are represented having both the first common namespace prefix, the second
namespace prefix, and a third common namespace prefix that is a sub-namespace of the second common namespace prefix.
|