CA2551059A1 - Pipeline architecture for use with net-centric application program architectures - Google Patents
Pipeline architecture for use with net-centric application program architectures Download PDFInfo
- Publication number
- CA2551059A1 CA2551059A1 CA002551059A CA2551059A CA2551059A1 CA 2551059 A1 CA2551059 A1 CA 2551059A1 CA 002551059 A CA002551059 A CA 002551059A CA 2551059 A CA2551059 A CA 2551059A CA 2551059 A1 CA2551059 A1 CA 2551059A1
- Authority
- CA
- Canada
- Prior art keywords
- message
- activities
- pipeline architecture
- logical expression
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
A pipeline architecture for defining a model view controller-like framework in a message oriented middleware-type context, the pipeline architecture comprising a plurality of activities for specifying how a pipeline processing component should handle a particular type of message or message sub-element; at least one activity plan for assembling a plurality of the plurality of activities together to define how a received message should be processed; and a selector framework for defining at least one logical expression that specifies at least one condition under which at least one activity should be applied to at least one message and/or at least one message sub-element.
Claims (21)
1. A pipeline architecture for defining a model view controller-like framework in a message oriented middleware-type context, the pipeline architecture comprising:
a plurality of activities for specifying how a pipeline processing component should handle a particular type of message or message sub-element;
at least one activity plan for assembling a plurality of the plurality of activities together to define how a received message should be processed; and a selector framework for defining at least one logical expression that specifies at least one condition under which at least one activity should be applied to at least one message and/ or at least one message sub-element.
a plurality of activities for specifying how a pipeline processing component should handle a particular type of message or message sub-element;
at least one activity plan for assembling a plurality of the plurality of activities together to define how a received message should be processed; and a selector framework for defining at least one logical expression that specifies at least one condition under which at least one activity should be applied to at least one message and/ or at least one message sub-element.
2. The pipeline architecture of claim 1 wherein the at least one activity plan includes a plurality of sections selected from the group consisting of: a redelivered message section, a message processing section, a message element section, an output section, a message error handling section, and a message element error handling section.
3. The pipeline architecture of claim 1 wherein the selector framework provides a mechanism for specifying a plurality of identifiers of different types that may be used within a plurality of selector expressions thereby making the selector framework customizable to a plurality of contexts.
4. The pipeline architecture of claim 3 wherein the at least one logical expression is expressed using standard query language.
5. A method of defining a model view controller-like framework in a message oriented middleware-type context, the method comprising:
receiving a message with destination code included in a message oriented middleware application;
retrieving an activity plan that includes a plurality of activities, wherein the activity plan is associated with the message oriented middleware application;
and selectively executing activities included in the activity plan to process the received message based on a logical expression represented in the received message;
selectively executing activities in the activity plan to develop an output message based on the results of the processing of the received message with the logical expression; and generating the output message for receipt by an application.
receiving a message with destination code included in a message oriented middleware application;
retrieving an activity plan that includes a plurality of activities, wherein the activity plan is associated with the message oriented middleware application;
and selectively executing activities included in the activity plan to process the received message based on a logical expression represented in the received message;
selectively executing activities in the activity plan to develop an output message based on the results of the processing of the received message with the logical expression; and generating the output message for receipt by an application.
6. The method of claim 5, wherein the logical expression comprises a plurality of logical expressions and selectively executing activities included in the activity plan to process the received message based on a logical expression represented in the received message comprises executing activities related to the received message as a whole at a message level, and executing activities related to individual elements included in the received message at a message element level based on the identification of the respective activities with the logical expressions.
7. The method of claim 5, wherein selectively executing activities comprises executing application specific activities based on the logical expression, and in view of the state of the application.
8. The method of claim 5, wherein selectively executing activities comprises filtering the activities in the activity plan with the logical expression to identify those activities that are to be applied to the received message.
9. The method of claim 5, wherein selectively executing activities comprises applying the logical expression to the activities in the activity plan based on the received message to determine the activities to be applied to the received message.
10. The method of claim 9, wherein applying the logical expression to the activities in the activity plan comprises determining whether activities should be applied to the entire received message or to an element included in the received message based on the logical expression.
11. The method of claim 5, wherein selectively executing activities comprises evaluating identifiers within the logical expression that are defined in one of a plurality of context specific ways.
12. The method of claim 5, wherein selectively executing activities comprises performing tasks within an application with the activities via an activity interface to the application.
13. A pipeline architecture for defining a model view controller-like framework in a message oriented middleware-type context, the pipeline architecture comprising:
a computer;
an application operable on the computer;
a message oriented middleware application operable on the computer, the message oriented middleware application configured to receive an incoming message;
an activity plan operable on the computer with the message oriented middleware, wherein the activity plan includes a plurality of activities that are selectively useable to process the incoming message;
a selector facility engine included in the message oriented middleware, the selector facility engine configured to evaluate at least one of a state of the application or a logical expression that is represented with the incoming message, or combinations thereof; and an activity selector included in the message oriented middleware to execute activities in the activity plan that are selected by the selector facility engine for execution.
a computer;
an application operable on the computer;
a message oriented middleware application operable on the computer, the message oriented middleware application configured to receive an incoming message;
an activity plan operable on the computer with the message oriented middleware, wherein the activity plan includes a plurality of activities that are selectively useable to process the incoming message;
a selector facility engine included in the message oriented middleware, the selector facility engine configured to evaluate at least one of a state of the application or a logical expression that is represented with the incoming message, or combinations thereof; and an activity selector included in the message oriented middleware to execute activities in the activity plan that are selected by the selector facility engine for execution.
14. The pipeline architecture of claim 13 further comprising an activity interface that is an executable activity operable to interface with the application and perform a task within the application.
15. The pipeline architecture of claim 13 wherein the logical expression comprises an identifier, and the selector facility engine is operable to evaluate the identifier in a predefined context specific way.
16. The pipeline architecture of claim 13 wherein the incoming message includes a plurality of message elements, and the logical expression is operable to determine the selected activities that are applied to the entire incoming message, and the selected activities that are applied to individual elements included in the incoming message.
17. The pipeline architecture of claim 13 wherein the message oriented middleware application is configurable to allow one system to publish data to a work queue in communication with the computer, and allow a second system in communication with the computer to subscribe to messages that are generated based on the published data, wherein the messages are processed by the message oriented middleware application and output from the message oriented middleware application for receipt by the second system.
18. The pipeline architecture of claim 13 wherein the activity plan includes activities directed to a plurality of different processing components that are selectively assembled in response to the incoming message, wherein the processing components include a message processing component, an output message production component, an error handling component, and a message redelivery component.
19. The pipeline architecture of claim 13 wherein the activity plan comprises a message section that includes activities that are selectively executable on the incoming message as a whole, and a message element section that includes activities that are selectively executable on elements included in the incoming message.
20. The pipeline architecture of claim 13 wherein the activity plan comprises an error handling section that includes activities that are selectively executable on the incoming message as a whole, or on elements included in the incoming message, or combinations thereof.
21. The pipeline architecture of claim 13 wherein the activity plan comprises an output section that includes activities that are selectively executable to produce an output message in response to processing of the incoming message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA2551059A CA2551059C (en) | 2002-05-17 | 2002-05-17 | Pipeline architecture for use with net-centric application program architectures |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA2446809A CA2446809C (en) | 2001-05-17 | 2002-05-17 | General and reusable components for defining net-centric application program architectures |
| CA2551059A CA2551059C (en) | 2002-05-17 | 2002-05-17 | Pipeline architecture for use with net-centric application program architectures |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2446809A Division CA2446809C (en) | 2001-05-17 | 2002-05-17 | General and reusable components for defining net-centric application program architectures |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2551059A1 true CA2551059A1 (en) | 2002-11-21 |
| CA2551059C CA2551059C (en) | 2011-04-19 |
Family
ID=36939002
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2551025A Expired - Lifetime CA2551025C (en) | 2002-05-17 | 2002-05-17 | Application framework for use with net-centric program architectures |
| CA2551059A Expired - Lifetime CA2551059C (en) | 2002-05-17 | 2002-05-17 | Pipeline architecture for use with net-centric application program architectures |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2551025A Expired - Lifetime CA2551025C (en) | 2002-05-17 | 2002-05-17 | Application framework for use with net-centric program architectures |
Country Status (1)
| Country | Link |
|---|---|
| CA (2) | CA2551025C (en) |
-
2002
- 2002-05-17 CA CA2551025A patent/CA2551025C/en not_active Expired - Lifetime
- 2002-05-17 CA CA2551059A patent/CA2551059C/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| CA2551025C (en) | 2016-11-22 |
| CA2551059C (en) | 2011-04-19 |
| CA2551025A1 (en) | 2002-11-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110648054B (en) | Task parallel processing method and device for robot flow automation | |
| CN101258469B (en) | Information processing device | |
| US8375372B2 (en) | Business process execution language program simulation | |
| JP2020531976A (en) | A device that provides a set of cryptographically protected, filtered, and sorted transaction datasets for blockchain links. | |
| CN111031133B (en) | Operation method and device of business engine, storage medium and electronic device | |
| WO2009106901A8 (en) | Improvements relating to handling and processing of massive numbers of processing instructions in real time | |
| CN100362479C (en) | System and method for testing measured object based on automatic test script | |
| CN103595770B (en) | Method and device for achieving file downloading through SDK | |
| CN104850491A (en) | Software test method, equipment and system | |
| CN102821211A (en) | Automatic testing method and device for communication network elements | |
| CN108287923B (en) | Intelligent visual interface data extraction system and design method thereof | |
| WO2006083046A3 (en) | Methods and apparatus for providing a task change application programming interface | |
| CN110891083A (en) | Agent method for supporting multi-job parallel execution in Gaia | |
| CN118132227A (en) | Agent scheduling method, system, equipment and medium based on large language model | |
| CA2551059A1 (en) | Pipeline architecture for use with net-centric application program architectures | |
| CN117314139A (en) | Modeling method and device for business process, terminal equipment and storage medium | |
| CN109558120A (en) | A kind of ecological cloud platform data entry system and application method based on big data | |
| CN110928668B (en) | ZooKeeper-based cloud task scheduling method and system | |
| CN111949326A (en) | Micro-service workflow method based on Activiti | |
| CN113326237A (en) | Log data processing method and device, terminal device and storage medium | |
| CN103197959B (en) | A kind of changing method of multi-core CPU | |
| CN111339422A (en) | Recommendation system task management platform, recommendation method and system | |
| CN107291455B (en) | Method and system for realizing transfer service based on factory mode | |
| Chacón et al. | Rapid application development using agent itinerary patterns | |
| Plaice et al. | Intensional communities |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKEX | Expiry |
Effective date: 20220517 |