Service interface
First Claim
Patent Images
1. A system for wrapping a software application to a service protocol, said system comprising:
- a computer;
a software application that has been developed independent from any service protocol; and
a processing framework comprising;
a dispatching unit, wherein the dispatching unit receives a task from the software application to be executed on the computer;
a production unit, wherein the production unit generates the task to be executed from the dispatching unit, bundles the task into a task block, the task block comprising a defined maximum number of tasks, and divides the bundled task into separate processing units, wherein the production unit does not generate additional tasks until all of the bundled tasks within the task block have been executed;
a configuration source comprising instructions for operation of the system to (i) select a service protocol based on information related to each processing unit-and (ii) specify a relationship between each processing unit and the service protocol; and
a service interface, wherein the service interface wraps the processing unit to the service protocol that was selected based on the instructions in the configuration source upon execution of the processing unit.
1 Assignment
0 Petitions
Accused Products
Abstract
A service interface enables an application to be developed independently from a particular service. At execution of the application, the application is wrapped or bound to a service. Advantageously, a configuration file includes instructions that bind particular applications with a particular service. Therefore, if improved services are developed after the application is written, only the configuration file needs to be updated, not the application source code. Accordingly, significant time and expense is saved by allowing applications to be developed independently from particular services.
-
Citations
15 Claims
-
1. A system for wrapping a software application to a service protocol, said system comprising:
-
a computer; a software application that has been developed independent from any service protocol; and a processing framework comprising; a dispatching unit, wherein the dispatching unit receives a task from the software application to be executed on the computer; a production unit, wherein the production unit generates the task to be executed from the dispatching unit, bundles the task into a task block, the task block comprising a defined maximum number of tasks, and divides the bundled task into separate processing units, wherein the production unit does not generate additional tasks until all of the bundled tasks within the task block have been executed; a configuration source comprising instructions for operation of the system to (i) select a service protocol based on information related to each processing unit-and (ii) specify a relationship between each processing unit and the service protocol; and a service interface, wherein the service interface wraps the processing unit to the service protocol that was selected based on the instructions in the configuration source upon execution of the processing unit. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer-implemented method for wrapping a software application to a service protocol, said method comprising:
-
receiving a task from a software application via a computer and generating the task for execution, wherein the software application has been developed independent from any service protocol; bundling the task into a task block, the task block comprising a defined maximum number of tasks, wherein additional tasks are not generated for execution until all of the bundled tasks within the task block have been executed; dividing the bundled task into separate processing units via the computer; accessing a configuration source via the computer, wherein the configuration source comprises instructions for (i) selecting a service protocol based on information related to each processing unit and (ii) specifying a relationship between each processing unit and the service protocol; and wrapping each processing unit to the service protocol that was selected based on the instructions of the configuration source upon execution of the processing unit. - View Dependent Claims (11, 12, 13, 14, 15)
-
Specification