Pipeline architecture for use with net-centric application program architectures
First Claim
1. A computer readable storage medium operable to store computer executable instructions for a pipeline architecture for defining a model view controller-like framework in a message oriented middleware-type context, the computer readable medium comprising:
- a plurality of activities specifying how a pipeline processing component should handle a particular type of message or message sub-element, each of the activities being a specific task executed to process the particular type of message, or to process the message sub-element of the particular type of message;
an activity plan comprising a subset of the plurality of activities, the activity plan assembled together to define how a received message having message sub elements should be processed; and
a selector framework defining at least one logical selector expression comprising a variable and an operator, the at least one logical selector expression specifying at least one condition upon which to selectively filter the plurality of activities included in the activity plan such that less than all of the plurality of activities included in the activity plan are assembled by the selector framework into a series of tasks forming a cohesive process, the activities included in the cohesive process executed with the selector framework to address a particular message related circumstance by application of the series of tasks to at least one of the received message and the message sub-elements.
2 Assignments
0 Petitions
Accused Products
Abstract
A robust toolkit provides facilities that can be assembled in a modular manner to specify the fundamental architecture of a net-centric application. A bootstrapping process assembles various facilities within the architecture. A configuration facility defines an API for getting properties that can be defined in any number of different types of sources. A factory de-couples how a resource is produced from where the resource is used. A selector framework applies standard query language to contexts other than querying a database. A pipeline architecture defines a model view controller-like framework for a processing pipeline. Selectors are used to specify when certain portions of a Web conversation should be made available to a user. An authorization facility associates permissions with a user to specify which portions of an application a user is authorized to use.
47 Citations
26 Claims
-
1. A computer readable storage medium operable to store computer executable instructions for a pipeline architecture for defining a model view controller-like framework in a message oriented middleware-type context, the computer readable medium comprising:
-
a plurality of activities specifying how a pipeline processing component should handle a particular type of message or message sub-element, each of the activities being a specific task executed to process the particular type of message, or to process the message sub-element of the particular type of message; an activity plan comprising a subset of the plurality of activities, the activity plan assembled together to define how a received message having message sub elements should be processed; and a selector framework defining at least one logical selector expression comprising a variable and an operator, the at least one logical selector expression specifying at least one condition upon which to selectively filter the plurality of activities included in the activity plan such that less than all of the plurality of activities included in the activity plan are assembled by the selector framework into a series of tasks forming a cohesive process, the activities included in the cohesive process executed with the selector framework to address a particular message related circumstance by application of the series of tasks to at least one of the received message and the message sub-elements. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method of defining a model view controller-like framework in a message oriented middleware-type context, the method comprising:
-
receiving a message with a server computer executing destination code included in a message oriented middleware application; retrieving with the server computer an activity plan that includes a plurality of activities, wherein the activity plan is associated with the message oriented middleware application; the server computer applying a first selector expression comprising a first variable and a first operator to the activity plan to identify a first subset of the activities included in the activity plan, the first selector expression associated with the received message or a state of the message oriented middleware application; the server computer assembling the first subset of activities into a first series of tasks forming a first cohesive process and executing the identified first subset of activities as the first series of tasks to process the received message; the server computer applying a second selector expression comprising a second variable and a second operator to the activities in the activity plan to identify a second subset of the activities in the activity plan; the server computer assembling the second subset of activities into a second series of tasks forming a second cohesive process and executing the identified second subset of activities as the second series of tasks to develop an output message based on the results of the processing of the received message with the first series of tasks; and generating the output message with the server computer for receipt by an application. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A system for defining a model view controller-like framework in a message oriented middleware-type context, the system comprising:
-
a computer having a memory; an application stored in the memory and executable on the computer; a message oriented middleware module stored in the memory and executable on the computer, the message oriented middleware module configured to receive an incoming message; an activity plan stored in the memory and executable on the computer with the message oriented middleware module, wherein the activity plan includes a plurality of activities that are selectively useable to process the incoming message each of the activities being a specific task executed to process a particular type of message; a selector facility engine included in the message oriented middleware module and executable on the computer, the selector facility engine configured to evaluate a plurality of selector expressions in view of at least one of a state of the application or information in the incoming message, or combinations thereof, each of the selector expressions comprising a variable and an operator; and an activity selector included in the message oriented middleware module and executable on the computer, the activity selector configured to test for those selector expressions that are applicable to the activities in the activity plan, the activity selector further configured to filter the activity plan using at least one of the applicable selector expressions identified from the test to assemble a subset of the activities from the activity plan as a series of tasks, the activity selector further configured to execute the subset of the activities in the activity plan to process the incoming message. - View Dependent Claims (20, 21, 22, 23, 24, 25, 26)
-
Specification