Legal claims defining the scope of protection, as filed with the USPTO.
1. A computer implemented method of generating a web services description document for a non-web services capable application programming interface function of an application, the method comprising: identifying, by a computer system, at least one function of a non-web services capable application programming interface and at least one function parameter; identifying, by the computer system, a type of synchrony associated with the function; identifying, by the computer system, desired types of synchrony for corresponding web services requests for said function, wherein the desired types of synchrony can include more than one type of synchrony; determining, by the computer system, a namespace corresponding to the application from the name of the function of the application programming interface; determining, by the computer system, a name of the corresponding web services request; determining, by the computer system, a system namespace for processing responses to asynchronous web services requests, wherein the system namespace is associated with a general services routine of a translation layer and is different from the namespace corresponding to the application; and generating, by the computer system, a web services description document including a type section associating the name of the corresponding web services request with the namespace, a message section associating the function parameter with a web services message, and a port section associating the web services message with a corresponding web services request, wherein the web services description document contains operations for all the identified types of synchrony corresponding to the function, wherein the web services description document further indicates that a response to the asynchronous web services request are obtained from the general services routine such that a token associated with the system namespace diverts the asynchronous web services request to the general processing routine of the translation layer.
2. The method of claim 1 , wherein the type section includes an association of the function parameter and the namespace.
3. The method of claim 1 , wherein in response to the type of synchrony of the application being synchronous and the desired type of synchrony being asynchronous, the type section includes an association of the function parameter and an alternate namespace associated with a web services layer.
4. The method of claim 1 , wherein the name of the corresponding web services request is determined from a name of the function using a naming convention.
5. The method of claim 1 , wherein the web services message is an input to a web services request.
6. The method of claim 1 , wherein the web services message is an output of web services request.
7. A non-transitory computer readable medium embodying a set of instructions to direct a computer to perform an operation comprising: identifying at least one function of a non-web services capable application programming interface and at least one function parameter; identifying a type of synchrony associated with the function; identifying desired types of synchrony for corresponding web services requests for said function, wherein the desired types of synchrony can include more than one type of synchrony; determining a namespace corresponding to the application from the name of the function of the application programming interface; determining a name of the corresponding web services request; determining, by the computer system, a system namespace for processing responses to asynchronous web services requests, wherein the system namespace is associated with a general services routine of a translation layer and is different from the namespace corresponding to the application; and generating a web services description document including a type section associating the name of the corresponding web services request with the namespace, a message section associating the function parameter with a web services message, and a port section associating the web services message with a corresponding web services request, wherein the web services description document contains operations for all the identified types of synchrony corresponding to the function, wherein the web services description document further indicates that a response to the asynchronous web services request are obtained from the general services routine such that a token associated with the system namespace diverts the asynchronous web services request to the general processing routine of the translation layer.
8. The non-transitory computer readable medium of claim 7 , wherein the type section includes an association of the function parameter and the namespace.
9. The non-transitory computer readable medium of claim 7 , wherein in response to the type of synchrony of the application being synchronous and the desired type of synchrony being asynchronous, the type section includes an association of the function parameter and an alternate namespace associated with a web services layer.
10. The non-transitory computer readable medium of claim 7 , wherein the name of the corresponding web services request is determined from a name of the function using a naming convention.
11. The non-transitory computer readable medium of claim 7 , wherein the web services message is an input to a web services request.
12. The non-transitory computer readable medium of claim 7 , wherein the web services message is an output of web services request.
13. A system configured to generate a web services description document for a non-web services capable application programming interface function of an application, the system comprising: a processor; and a memory storing a set of instructions that configure the processor to: identify at least one function of a non-web services capable application programming interface and at least one function parameter; identify a type of synchrony associated with the function; identify desired types of synchrony for corresponding web services requests for said function, wherein the desired types of synchrony can include more than one type of synchrony; determine a namespace corresponding to the application from the name of the function of the application programming interface; determine a name of the corresponding web services request; determine a system namespace for processing responses to asynchronous web services requests, wherein the system namespace is associated with a general services routine of a translation layer and is different from the namespace corresponding to the application; and generate a web services description document including a type section associating the name of the corresponding web services request with the namespace, a message section associating the function parameter with a web services message, and a port section associating the web services message with a corresponding web services request, wherein the web services description document contains operations for all the identified types of synchrony corresponding to the function, wherein the web services description document further indicates that a response to the asynchronous web services request are obtained from the general services routine such that a token associated with the system namespace diverts the asynchronous web services request to the general processing routine of the translation layer.
14. The system of claim 13 , wherein the type section includes an association of the function parameter and the namespace.
15. The system of claim 13 , wherein in response to the type of synchrony of the application being synchronous and the desired type of synchrony being asynchronous, the type section includes an association of the function parameter and an alternate namespace associated with a web services layer.
16. The system of claim 13 , wherein the name of the corresponding web services request is determined from a name of the function using a naming convention.
17. The system of claim 13 , wherein the web services message is an input to a web services request.
18. The system of claim 13 , wherein the web services message is an output of web services request.
Unknown
May 14, 2013
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.