Method and system of performing transactions using shared resources and different applications
A method and system can comprise a software architecture that allows different applications in the same or different communications protocols to interact with shared resources. More specifically, code for a computer program may be written to increase the amount of code that is generic to (i.e., shared by) more than one application or communications protocol and reduce the amount of code that handle application-specific or protocol-specific actions. In one embodiment, a transaction may be broken down into a set of discrete actions. The discrete actions may include functions that are common to more than one application. These functions may be part of the shared resources. Each application may have its own set of software plug-in modules for the discrete actions.
1. A computer-implemented method for processing a transaction, comprising:
providing a set of applications, wherein each application is configured to implement the transaction and wherein the transaction comprises a set of ordered stages;
providing a set of modules for each of the ordered stages, wherein each set of modules is capable of implementing functionality associated with one ordered stage; and
providing a shared set of resources, wherein the resources are each operable to be utilized by the modules,
wherein each application comprises modules from one or more of the sets of modules,
wherein each application is configured for use with a request in a protocol,
wherein one of the ordered stages is a request reception stage, and each module within the set of modules for the request reception stage is configured for use with a protocol,
wherein each module within the set of modules for the request reception stage is operable to convert the request into a generic format,
wherein each application includes a module from the set of modules for the request reception stage; the module and the application are configured for use with the same protocol; and the other modules comprising the application are configured for use with the generic format.
2. The method of claim 1 , further comprising processing the request with one application from the set of applications.
3. The method of claim 2 , wherein processing the request comprises
converting the request to the generic format using the module from the set of modules for the request reception stage; and
processing the request in the generic format using the other modules of the application.
4. The method of 1 , wherein the ordered stages include request reception, request authorization, request manipulation, content retrieval, content manipulation, content response.
5. The method of claim 4 , wherein the shared resources include a content cache, a parameter cache, a connection pool, a domain name server, a clock, a counter, a database, or a global variable space.
6. The method of claim 1 , wherein the generic format is an associative array, including data from the header or content portion of the request.
7. A computer system for processing a transaction, comprising:
a set of applications, wherein each application is configured to implement the transaction and wherein the transaction comprises a set of ordered stages;
a set of modules for each of the set of ordered stages, wherein each set of modules is capable of implementing functionality associated with one ordered stage; and
a shared set of resources, wherein the resources are each operable to be utilized by the modules,
wherein each application comprises modules from one or more of the sets of modules,
wherein each application is configured for use with a request in a protocol,
wherein one of the ordered stages is a request reception stage, and each module within the set of modules for the request reception stage is configured for use with a protocol,
wherein each module within the set of modules for the request reception stage is operable to convert the request into a generic format,
wherein each application includes a module from the set of modules for the request reception stage; the module and the application are configured for use with the same protocol; and the other modules comprising the application are configured for use with the generic format.
8. The system of claim 7 , wherein the system is operable to process the request using one application from the set of applications.
9. The system of claim 8 , wherein processing the request comprises
converting the request to the generic format using the module from the set of modules for the request reception stage; and
processing the request in the generic format using the other modules of the application.
10. The system of claim 7 , wherein the ordered stages include request reception, request authorization, request manipulation, content retrieval, content manipulation, content response.
11. The system of claim 10 , wherein the shared resources include a content cache, a parameter cache, a connection pool, a domain name server, a clock, a counter, a database, or a global variable space.
12. The system of claim 7 , wherein the generic format is an associative array, including data from the header or content portion of the request.
13. A data processing system readable medium having code embodied therein for processing a transaction, the code comprising instructions translatable for implementing:
a set of applications, wherein each application is configured to implement the transaction and wherein the transaction comprises a set of ordered stages;
a set of modules for each of the set of ordered stages, wherein each set of modules is capable of implementing functionality associated with one ordered stage; and
a shared set of resources, wherein the resources are each operable to be utilized by the modules,
wherein each application comprises modules from one or more of the sets of modules,
wherein each application is configured for use with a request in a protocol,
wherein one of the ordered stages is a request reception stage, and each module within the set of modules for the request reception stage is configured for use with a protocol,
wherein each module within the set of modules for the request reception stage is operable to convert the request into a generic format,
wherein each application includes a module from the set of modules for the request reception stage; the module and the application are configured for use with the same protocol; and the other modules comprising the application are configured for use with the generic format.
14. The data processing system readable medium of claim 13 , further comprising wherein the instructions are further translatable to process the request using one application from the set of applications.
15. The data processing system readable medium of claim 14 , wherein processing the request comprises:
converting the request to the generic format using the module from the set of modules for the request reception stage; and
processing the request in the generic format using the other modules of the application.
16. The data processing system readable medium of claim 13 , wherein the ordered stages include request reception, request authorization, request manipulation, content retrieval, content manipulation, content response.
17. The data processing system readable medium of claim 16 , wherein the shared resources include a content cache, a parameter cache, a connection pool, a domain name server, a clock, a counter, a database, or a global variable space.
18. The data processing system readable medium of claim 13 wherein the generic format is an associative array, including data from the header or content portion of the request.