Inventors list |
Assignees list |
Classification tree browser |
Top 100 Inventors |
Top 100 Assignees |
Luttinen, WA
Todd Luttinen, Redmond, WA US
| Patent application number | Description | Published |
|---|---|---|
| 20090006564 | HIGH AVAILABILITY TRANSPORT - A system provides high availability electronic message forwarding. When an electronic message is communicated to a first server, a copy of the electronic message is maintained at a second server. The electronic message is maintained on both servers until the electronic message is successfully communicated to a third server. After the message is delivered to the third server, the electronic message is removed from both the first server and the second server. If the first server fails to communicate the electronic message to the third server, the second server does so. | 01-01-2009 |
| 20090327361 | DATA REPLICATION FEEDBACK FOR TRANSPORT INPUT/OUTPUT - Architecture for efficiently ensuring that data is stored to the desired destination datastore such as for replication processes. A copy of data (e.g., messages) sent to a datastore for storage is stored at an alternate location until a received signal indicates that the storage and replication was successful. As soon as the feedback signal is received, the copy is removed from the alternate location, and hence, improves input/output (I/O) and storage patterns. The feedback mechanism can also be used for monitoring the status of data transport associated with log shipping, for example, and taking the appropriate actions when storage (e.g., replication) is not being performed properly. | 12-31-2009 |
Todd C. Luttinen, Redmond, WA US
| Patent application number | Description | Published |
|---|---|---|
| 20100191810 | TRANSPORT HIGH AVAILABILITY FOR SIDE EFFECT MESSAGES - Architecture that protects side effect messages by associating the side effect messages with a primary (redundant) message that was received by a transport mechanism (e.g., a message transport agent). Side effect messages are considered “side effects” of a primary message that caused generation of the side effect messages. The primary message is only considered fully delivered after the primary message and all associated side effect messages are delivered, after which the source of the primary message is ACK'd (sent an “ACKnowledgement” message). Hence, in case of hardware failures after the primary message was delivered, but before delivery of side effect messages, the redundancy approach used triggers re-delivery of the primary message and re-generation and delivery of the side effect messages. | 07-29-2010 |
| 20100205257 | TRANSPORT HIGH AVAILABILITY VIA ACKNOWLEDGE MANAGEMENT - Architecture that facilitates transport high availability for messaging services by providing the ability of a receiving entity (e.g., receiving message transfer agent (MTA)) to detect if a sending entity (e.g., sending MTA or client) is a legacy sending entity. When the receiving entity detects that the sending entity is a legacy system, by advertising transport high availability capability to the sending entity, if the sending entity does not opt-in to this capability, the receiving entity keeps the sending entity client “on hold”, that is, waiting for an acknowledgement (ACK) until the receiving entity delivers the message to the next hops (immediate destinations). This approach maintains at least two copies of the message until the message is successfully delivered (to the next hop(s)). Hence, if the legacy sending entity or the receiving entity fails, the message is still delivered successfully. | 08-12-2010 |
| 20100325215 | MESSAGE REQUIREMENTS BASED ROUTING OF MESSAGES - Architecture for enabling messages to be routed between network servers based on message requirements related to version, capabilities, and features, for example. The message requirements designate delivery over a transport path compatible with the message requirements. The message requirements can include a particular version or other features related to different software applications that require compatibility in message handling. Routing information is maintained related to a transport server or other network transport entity compatible with the message requirements and through which the message can be routed. The message is routed to the compatible transport server for delivery to the destination while avoiding delivery to transport servers incompatible with the message requirements. | 12-23-2010 |
Todd Carlyle Luttinen, Redmond, WA US
| Patent application number | Description | Published |
|---|---|---|
| 20100306321 | DELIVERING MESSAGES USING USER-DEFINED AGENTS - User-defined agents and connectors are defined to process messages for a messaging application. The user-defined agents are configured to extend the capabilities of the messaging application. Each user-defined agent is associated with a connector that is configured to route messages for a particular address space according to the specified protocol. Upon receipt of a routed message within the particular address space, the messaging application on the server invokes the associated user-defined agent to process the message. The user-defined agent utilizes an API that is associated with the messaging application to assist in processing the message. | 12-02-2010 |
| 20100306323 | DETAILED END-TO-END LATENCY TRACKING OF MESSAGES - Latency information is collected for each message as it moves through an organization. The latency information includes latency information for components processing the message. When the message is routed to the next server within the organization, the collected latency information for the server sending the message is included with the message. The collected latency information is written to a message tracking log when it either is delivered within the organization or when the message leaves the organization. The message tracking log may then be viewed such that the collected latency information may be viewed and analyzed. | 12-02-2010 |