Patent application number | Description | Published |
20080294971 | TRANSPARENT ENVELOPE FOR XML MESSAGES - Transforming portions of a message to a destination via a communication protocol. A message is received. It is detected whether the received message includes an encoded envelope. The encoded envelope includes a stack defining parameters including information for handling the received message in an original format. If the received message includes the encoded envelope, the defined parameters are transformed to coded parameters in a common format. The coded parameters express the same information for handling the received message in the communication protocol. The encoded envelope is encapsulated in the received message, and the received message in the common format is delivered to the destination. If the received message does not include an encoded envelope, coded parameters are generated in the common format for the received message by encoding addressing information from the received message. The received message having the coded parameters in the common format is delivered to the destination. | 11-27-2008 |
20090049197 | LIGHTWEIGHT ADDRESS FOR WIDELY-DISTRIBUTED ADHOC MULTICAST GROUPS - Delivery of a message over a communications network from a sender based on a single delivery address. The single delivery address is generated as one unit for the message. The single delivery address has a collection of recipient addresses including one or more recipient addresses each identifying at least one recipient of the message. Each of the one or more recipient addresses includes a user level information and a domain level information. The generated single delivery address with the collection of recipient addresses is included in the message. A copy of the message is provided to the identified recipient(s) as a function of the domain level information of the one or more recipient addresses. The message is transmitted over the communications network to the identified recipient(s) recipient based on the collection of recipient addresses. | 02-19-2009 |
20100057707 | QUERY-ORIENTED MESSAGE CHARACTERIZATION - Processing messages. Messages are processed based on a characteristic derived from information in messages, metadata about messages, or other information external to messages. Values for one or more pieces of information are received. At least one of the values for one or more pieces of information is associated with a first message. Queries are received. The queries specify one or more of the pieces of information. At least a portion of the plurality of values for the one or more pieces of information is processed in conjunction with the one or more queries to create one or more normalized characteristics for the first message. The one or more normalized characteristics for the first message are in a same format irrespective of the format of the pieces of information. The first message, and/or other messages, is processed based on at least one of the one or more normalized characteristics. | 03-04-2010 |
20110145684 | TRANSPARENT ENVELOPE FOR XML MESSAGES - Transforming portions of a message to a destination via a communication protocol. A message is received. It is detected whether the received message includes an encoded envelope. The encoded envelope includes a stack defining parameters including information for handling the received message in an original format. If the received message includes the encoded envelope, the defined parameters are transformed to coded parameters in a common format. The coded parameters express the same information for handling the received message in the communication protocol. The encoded envelope is encapsulated in the received message, and the received message in the common format is delivered to the destination. If the received message does not include an encoded envelope, coded parameters are generated in the common format for the received message by encoding addressing information from the received message. The received message having the coded parameters in the common format is delivered to the destination. | 06-16-2011 |
20110145685 | TRANSPARENT ENVELOPE FOR XML MESSAGES - Transforming portions of a message to a destination via a communication protocol. A message is received. It is detected whether the received message includes an encoded envelope. The encoded envelope includes a stack defining parameters including information for handling the received message in an original format. If the received message includes the encoded envelope, the defined parameters are transformed to coded parameters in a common format. The coded parameters express the same information for handling the received message in the communication protocol. The encoded envelope is encapsulated in the received message, and the received message in the common format is delivered to the destination. If the received message does not include an encoded envelope, coded parameters are generated in the common format for the received message by encoding addressing information from the received message. The received message having the coded parameters in the common format is delivered to the destination. | 06-16-2011 |
20130282655 | QUERY-ORIENTED MESSAGE CHARACTERIZATION - Processing messages. Messages are processed based on a characteristic derived from information in messages, metadata about messages, or other information external to messages. Values for one or more pieces of information are received. At least one of the values for one or more pieces of information is associated with a first message. Queries are received. The queries specify one or more of the pieces of information. At least a portion of the plurality of values for the one or more pieces of information is processed in conjunction with the one or more queries to create one or more normalized characteristics for the first message. The one or more normalized characteristics for the first message are in a same format irrespective of the format of the pieces of information. The first message, and/or other messages, is processed based on at least one of the one or more normalized characteristics. | 10-24-2013 |
Patent application number | Description | Published |
20080208979 | DISPATCHING CLIENT REQUESTS TO APPROPRIATE SERVER-SIDE METHODS - The present invention extends to methods, systems, and computer program products for dispatching client requests to appropriate server-side methods. When a client request is received, a Web server refers to a service contract framework that maps URI paths and HTTP methods to corresponding server implemented methods. A server implemented method corresponding to a URI path and/or an HTTP method included in the client request is identified. The server implemented method is invoked to process the client request message. Accordingly, embodiments of the invention provide a uniform mechanism to dispatch HTTP requests to designated server implemented methods based solely on URI path and HTTP method. That is, an HTTP request can be dispatched to a designated server implemented method without having to include additional dispatch metadata within the HTTP request (e.g., in a SOAP envelope). | 08-28-2008 |
20080270428 | UNIFORM RESOURCE IDENTIFIER TEMPLATE MANIPULATION - Data may be bound to a Uniform Resource Identifier (URI) template using a bind operation. Conversely, a URI may be matched against a URI template to result in data extracted from the URI. A URI may be matched against multiple URI templates using, for example, a template table to thereby generate an estimated best-match URI template for the URI, and potentially also return matched data extracted from the URI using the best-match URI template. | 10-30-2008 |
20100229152 | PRESCRIPTIVE ARCHITECTURE FOR APPLICATION DEVELOPMENT - A prescriptive architecture for application development is provided. In some embodiments, the architecture comprises a service, a receiver, a sender, and a transport. The service functions to perform the actual business logic, is decorated with service deployment metadata; and is operable to communicate via types. The receiver is coupled to the service and is generated entirely from the service deployment metadata. The receiver is operable to receive messages, convert the received messages into types, and communicate with the service using the types. The sender is coupled to the receiver and is generated entirely from the service deployment metadata. The sender functions as a proxy for the service to a service consumer, and is operable to communicate using types with the service consumer. The sender is operable to convert the types to messages, and communicate with the receiver via messages. The transport functions as a message exchange technology that allows the sender and receiver to communicate, and is designated by the service deployment metadata and implemented as an underlying technology of the sender and the receiver. | 09-09-2010 |
20100229154 | DECLARATIVE ASPECTS AND ASPECT CONTAINERS FOR APPLICATION DEVELOPMENT - An aspect container being operable to generate an instance of itself at run time is provided. The aspect container comprises logic operable to create an instance of the aspect container by reading configuration information specifying a sequence of one or more aspects from an aspect container configuration file corresponding to the aspect container. The logic is also operable to generate instances of the aspects in the sequence, configure each aspect instance with its configuration information from an aspect configuration file corresponding to the aspect, and chain the aspect instances according to the specified sequence, such that the chain of aspect instances preamble and postamble activities of a class or method. | 09-09-2010 |
20100325262 | USING TRANSPORT-INDEPENDENT RESOURCE STATUS - The present invention extends to methods, systems, and computer program products for using transport-independent resource status. Embodiments of the invention provide a mechanism for implementing a new protocol for performing resource request status updates that maintains the benefits of existing protocol (e.g., HTTP) conventions while being usable with arbitrary transport protocols. Additionally, the new protocol works with a variety of different message exchange patterns. The use of the protocol can be hidden behind a programming model that normalizes transport-specific resource status protocols, such as, for example, HTTP, with transport-independent resource status protocols, such as, for example, with a SOAP binding of the described protocol. As such, embodiments of the invention provide resource status updates over an arbitrary network transport protocol whose format and message exchange pattern is decoupled from the definition of the application. | 12-23-2010 |
20110258334 | USING TRANSPORT-INDEPENDENT RESOURCE STATUS - The present invention extends to methods, systems, and computer program products for using transport-independent resource status. Embodiments of the invention provide a mechanism for implementing a new protocol for performing resource request status updates that maintains the benefits of existing protocol (e.g., HTTP) conventions while being usable with arbitrary transport protocols. Additionally, the new protocol works with a variety of different message exchange patterns. The use of the protocol can be hidden behind a programming model that normalizes transport-specific resource status protocols, such as, for example, HTTP, with transport-independent resource status protocols, such as, for example, with a SOAP binding of the described protocol. As such, embodiments of the invention provide resource status updates over an arbitrary network transport protocol whose format and message exchange pattern is decoupled from the definition of the application. | 10-20-2011 |
Patent application number | Description | Published |
20080270624 | NORMALIZATION OF BINARY DATA - The transformation of data between binary data and hierarchical data, such as might be processed by an Infoset Processor. When data is received from a network in binary format, the transformation module transforms the binary data into a hierarchical data representation of the binary data, and then provides the transformed data to message processors (e.g., Infoset processors) that understand the hierarchical schema. The transformation module may also transform hierarchical data into binary data for transmission on a network. | 10-30-2008 |
20090234971 | ENCODING/DECODING WHILE ALLOWING VARYING MESSAGE FORMATS PER MESSAGE - Encoding and/or decoding of messages. On the encoding end, a composite encoder encodes message from an internal format that is used by internal system components into an external format. However, the composite encoder may encode the outgoing messages into different external formats on a per-message basis. For incoming message, a composite decoder decodes incoming messages from any one of a plurality of external formats into the internal format also on a per-message basis. A per-message report mechanism permits internal system components and the encoding/decoding components to communicate information regarding the encoding or decoding on a per message basis. This permits a higher level of collaboration and complexity in the encoding and decoding process. | 09-17-2009 |
20100169862 | INTERFACE INFRASTRUCTURE FOR A CONTINUATION BASED RUNTIME - Namespace for continuation-based runtime. Some embodiments described herein are directed to a framework using continuation based runtime namespaces that pertain to an infrastructure for enabling the creation of a wide variety of continuation-based programs that perform a wide-array of tasks. The infrastructure provides a foundation for building continuation-based, declarative applications of various scale and complexity. In some embodiments, the associated application programming interfaces (APIs) are factored into a hierarchy of namespaces in a manner that balances utility, usability, extensibility, and versionability. | 07-01-2010 |
20110231812 | WORKFLOW EXECUTION MODEL - Embodiments are directed to implementing a generalized workflow execution model configured to provide access to workflow elements. A computer system instantiates a generalized workflow execution model that provides access to workflow elements stored in a database that is connected to the workflow execution model. The workflow execution model includes the following: activity models that include both agents which are configured to express the control flow of the activity models and symbols which represent values usable by the activity models and metadata configured to identify the workflow execution model. The computer system also receives user input requesting workflow elements and accesses the database to provide the requested workflow elements using the generalized workflow execution model. | 09-22-2011 |
20110264702 | CONVERSION OF HIERARCHICAL INFOSET TYPE DATA TO BINARY DATA - Encoding and/or decoding of messages. On the encoding end, a composite encoder encodes message from an internal format that is used by internal system components into an external format. However, the composite encoder may encode the outgoing messages into different external formats on a per-message basis. For incoming message, a composite decoder decodes incoming messages from any one of a plurality of external formats into the internal format also on a per-message basis. A per-message report mechanism permits internal system components and the encoding/decoding components to communicate information regarding the encoding or decoding on a per message basis. XML messages can be converted automatically into Binary messages. | 10-27-2011 |
20120110204 | ENVELOPE ATTACHMENT FOR MESSAGE CONTEXT - A system for aggregating context information for messages includes a context container that associates names with context values and metadata for context entries. The system further includes a network protocol component configured to read messages from a network transport, an encoder component configured translate messages from a raw format into a canonical message format. The canonical message format is an enveloped message containing an application payload and message metadata. The context container is associated with a message in the canonical format. The system further includes an extraction component configured to retrieve context from a native network transport protocol and insert the context values and metadata into the context container, a plurality of additional protocol components configured to add, remove, or modify entries in the context container, and one or more higher level application components configured to operate on the canonical message using the context entries. | 05-03-2012 |
20130282681 | WORKFLOW EXECUTION MODEL - A generalized workflow execution model is configured to provide access to workflow elements. A computer system instantiates a generalized workflow execution model that provides access to workflow elements stored in a database that is connected to the workflow execution model. The workflow execution model includes the following: activity models that include both agents which are configured to express the control flow of the activity models and symbols which represent values usable by the activity models and metadata configured to identify the workflow execution model. The computer system also receives user input requesting workflow elements and accesses the database to provide the requested workflow elements using the generalized workflow execution model. | 10-24-2013 |