Interface infrastructure for creating and interacting with web services

• US 20060150200A1
• Filed: 12/03/2004
• Published: 07/06/2006
• Est. Priority Date: 12/03/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kaler, Christopher G., Eppley, Geary L., Cohen, Shy, Gajjala, Vijay K., Johnson, James E., Vernal, Michael Steven, Della-Libera, Giovanni M., Puri, Siddhartha, Janczuk, Tomasz, Osovetsky, Evgeny, Madan, Umesh, Wortendyke, David, Srinivasan, Krishnan, Christensen, Erik Bo, Swartz, Stephen T., Hegde, Uday S., Wolf, Kenneth David, Purdy, Douglas M., Pessach, Yaniv, Millet, Stephen J., Sturgell, Ryan Thomas, Marucheck, Michael Jon, Feingold, Max Attar, Walter, Douglas A., Doty, John David, Nog, Saurab, Dievendorff, Richard, Srinivasan, Sowmyanarayanan K., DeJarnatt, Alexander Martin, Batres, Stefan, Olson, Lance E., Gupta, Kapil, Vishwanath, Tirunelveli, Levin, David Edwin, Dice, Michael Thomas, Upadhyay, Chaitanya D., Ruiz-Scougall, Jesus, Ottaviani, Mauro, Kasiolas, Anastasios, Sverdlov, Serge, Waingold, Elliot Lee, Honeycutt, Erin P., Lee, Alfred M. IV, Shvets, Eugene, Driver, David Owen, Modi, Vipul Arunkant, Critchley, Craig Andrew, Stern, Aaron Abraham, Wheeler, Jonathan T., Balayogan, Vaithialingam B., Ramadan, Mohamed-Hany Essam, Makarechian, Mohammad, Shohoud, Yasser, Coulson, Michael James, Hill, Richard Douglas, Seely, Scott Christopher, Tavis, Matthew Thomas, Jethanandani, Natasha Harish, Pharies, Stefan Harrington, Rjagopalan, Anand
• Granted Patent: US 7,512,957 B2
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

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.

Claims

1. 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.

2. One or more computer-readable media in accordance with claim 1, wherein the first plurality of web services APIs are represented as source code.

3. One or more computer-readable media in accordance with claim 1, wherein the first plurality of web services APIs are represented as compiled code.

4. One or more computer-readable media in accordance with claim 1, wherein the first and second plurality of web services APIs are operable on the .NET platform.

5. One or more computer-readable media in accordance with claim 1, wherein the first common namespace is “

System.ServiceModel”

or is compiled from the text “

System.ServiceModel”

.

6. One or more computer-readable media in accordance with claim 5, wherein the second common namespace is “

System.ServiceModel.Channels”

or is compiled from the text “

System.ServiceModel.Channels”

.

7. One or more computer-readable media in accordance with claim 5, wherein the second common namespace is “

System.ServiceModel.Configuration”

or is compiled from the text “

System.ServiceModel.Configuration”

.

8. One or more computer-readable media in accordance with claim 5, wherein the second common namespace is “

System.ServiceModel.Design”

or is compiled from the text “

System.ServiceModel.Design”

.

9. One or more computer-readable media in accordance with claim 5, wherein the second common namespace is “

System.ServiceModel.Diagnostics”

or is compiled from the text “

System.ServiceModel.Diagnostics”

.

10. One or more computer-readable media in accordance with claim 5, wherein the second common namespace is “

System.ServiceModel.Security”

or is compiled from the text “

System.ServiceModel.Security”

.

11. One or more computer-readable media in accordance with claim 10, wherein the second common namespace is “

System.ServiceModel.Security.Protocols”

or is compiled from the text “

System.ServiceModel.Security.Protocols”

.

12. One or more computer-readable media in accordance with claim 1, further having thereon the following:

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 plurality of web services APIs, wherein each of the third plurality of web services APIs are represented having both the first common namespace prefix and a third common namespace prefix that is a sub-namespace of the first common namespace prefix.

13. One or more computer-readable media in accordance with claim 12, further having thereon the following:

a fourth 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 third plurality of web services APIs, wherein each of the fourth plurality of web services APIs are represented having both the first common namespace prefix, the third common namespace prefix and a fourth common namespace prefix that is a sub-namespace of the third common namespace prefix.

14. One or more computer-readable media in accordance with claim 1, further having thereon the following:

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.

15. One or more computer-readable media in accordance with claim 1, wherein the one or more computer-readable media are physical media.

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

a first plurality of APIs, each of which for implementing functions having first one or more common features, wherein each of the first plurality of APIs are represented with a first common namespace prefix for logical grouping of the first plurality of APIs; and

a second plurality of APIs, each of which for implementing functions having second one or more common features, wherein each of the second plurality of 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.

17. One or more computer-readable media in accordance with claim 16, wherein the first plurality of APIs are represented as source code.

18. One or more computer-readable media in accordance with claim 16, wherein the first plurality of APIs are represented as compiled code.

19. One or more computer-readable media in accordance with claim 16, wherein the first and second plurality of APIs are operable on the .NET platform.

20. One or more computer-readable media in accordance with claim 16, wherein the second common namespace is “

System.Security.Authorization”

or is compiled from the text “

System.Security.Authorization”

.

21. One or more computer-readable media in accordance with claim 16, wherein the second common namespace is “

System.Runtime.Serialization”

or is compiled from the text “

System.Runtime.Serialization”

.

22. One or more computer-readable media in accordance with claim 16, wherein the second common namespace is “

System.Transactions”

or is compiled from the text “

System.Transactions”

.

23. One or more computer-readable media in accordance with claim 16, wherein the second common namespace is “

System.IO.Log”

or is compiled from the text “

System.IO.Log”

.

24. One or more computer-readable media in accordance with claim 16, wherein the second common namespace is “

System.Text”

or is compiled from the text “

System.Text”

.

25. One or more computer-readable media in accordance with claim 16, wherein the second common namespace is “

System.Xml”

or is compiled from the text “

System.Xml”

.

26. One or more computer-readable media in accordance with claim 16, wherein the second common namespace is “

System.ServiceModel”

or is compiled from the text “

System. ServiceModel”

.

27. One or more computer-readable media in accordance with claim 16, wherein the message-passing application implements Web Services.

28. One or more computer-readable media in accordance with claim 16, wherein the one or more computer-readable media are physical media.