US 2010/0150031 A1Published application

Multiplexed communication for duplex applications

AssigneeMicrosoft Corporation

InventorsNicholas A. Allen, Stefan R. Batres, Philbert L. Henning, II, Margaret J. Lye, Evgeny Osovetsky

Life of this patent

Estimating the term…

Loading patent…

Abstract

The present invention extends to methods, systems, and computer program products for multiplexed communication for duplex applications. Embodiments of the invention facilitate a multiplexed variant of long polling over a request/reply communication medium that (potentially significantly) reduces the resources utilized when exchanging messages. The lightweight address generation mechanism facilitates polling and routing for a pool of many clients and many services while minimizing allocated resources to each established session. Further, the benefits of a lower latency bidirectional communication medium between clients and services can be utilized.

Claims25

Dependent claims

At a computer system including one or more processors and system memory, the computer system also including a duplex service component, the duplex service component communicating with one or more services over one or more duplex communication mediums and communicating with one or more duplex client components over one or more request/reply communication mediums, a method for transferring data in response to a client request, the method comprising:

an act of the duplex service component receiving a request for messages from a duplex client component using one of the one or more request/reply communication mediums, the request including an endpoint identifier identifying a client endpoint used between a corresponding duplex client component and the duplex service component, the corresponding duplex client component selected from among the one or more duplex client components, the corresponding duplex client component connected to a client;
an act of the duplex service component queuing the request in a read queue, the read queue configured to queue requests that are waiting for replies;
an act of the duplex service component receiving an application message from a service using one of the one or more duplex communication mediums, the application message including the endpoint identifier and a session identifier, the session identifier identifying a transfer session between the service and a client connected to the duplex client component;
an act of the duplex service component queuing the application message in a write queue, the write queue configured to queue application messages to return for subsequent client requests;
and
an act of the duplex service component sending a reply to the duplex client component using the request/reply communication medium, the reply sent to the duplex client component based on the endpoint identifier, the reply corresponding to the request that was received using the request/reply protocol.

3 more elements

At a computer system including one or more processors and system memory, the computer system also including a duplex client component, the duplex client component communicating with one or more clients over one or more duplex communication mediums and communicating with a duplex service component over a request/reply communication medium, a method for transferring data in response to a client request, the method comprising:

an act of the duplex client component receiving an application message from a client using one of the one or more duplex communication mediums;
an act of the duplex client component formulating the application message into a request of a request/reply protocol, the request including an endpoint identifier and a session identifier, the endpoint identifier identifying the client endpoint used between the duplex client component and the duplex service component, the session identifier identifying a particular connection between the client and a service from among all the connections between the duplex client component and the duplex service component;
an act of the duplex client component sending the request to the duplex service component using the request/reply communication medium;
and
an act of the duplex client component receiving a reply from the duplex service component using the request/reply communication medium, the reply sent to the duplex client component based on the endpoint identifier, the reply corresponding to the request sent using the request/reply communication medium.

2 more elements

A network system, including one or more clients, one or more duplex client components, a duplex service component, and one or more services, each of the one or more clients connected to one of the one or more duplex client components on a network over one or more duplex communication mediums, each of the one or more duplex client components connected to the duplex service component on the network over one or more request/reply communication mediums, and the duplex service component connected to each of the one or more services on the network over one or more duplex communication mediums, the network system comprising:

a duplex service component computer system, the duplex service component computer system including:
one or more processors;
system memory;
and
one or more physical storage media having stored thereon computer-executable instructions representing a duplex service component, wherein the duplex service component is configured to:
receive client application messages, batches of client application messages, and requests for application messages from duplex client components using HyperText Transfer Protocol, the requests for application messages being poll messages that include endpoint identifiers, the endpoint identifiers identifying client endpoints used between a corresponding duplex client component and the duplex service component;
queue received requests in a read queue;
forward client application messages to the appropriate service using one of the duplex communication mediums;
receive service application messages from services using the one or more duplex communication mediums, the application messages including endpoint identifiers identifying client endpoints and a session identifier identifying a particular connection between a client and the service from among all of the connections between the duplex client component and duplex service component;
queue server application messages in a write queue;
and
send replies to the duplex client components using the HTTP protocol, replies including one of:
an application message including an endpoint and session identifier, a batch of application messages, and an idle message;
and
one or more duplex client component computer systems, each duplex client computer system including:
one or more processors;
system memory;
and
one or more physical storage media having stored thereon computer-executable instructions representing a duplex client component, wherein the duplex client component is configured to:
receive client application messages from clients using the one or more duplex communication mediums;
generate requests for service application messages on behalf of the clients connected to the duplex client component;
formulate client communication into HypterText Transfer Protocol messages, including formulating requests for service application messages into poll messages in the HyperText Transfer Protocol, the poll messages including endpoint identifiers, the endpoint identifiers identifying the client endpoint used between the duplex client component and the duplex service component, the client application messages including endpoint and session identifiers, the session identifiers identifying a particular connection between the client and a service from among all the connections between the duplex client component and the duplex service component;
send client communication to the duplex service component using HyperText Transfer Protocol;
and
receive replies from the duplex service component using HyperText Transfer Protocol, replies including one of:
an application message including an endpoint and session identifier, a batch of application messages, and an idle message.

23 more elements

Dependencies are inferred from the claim text.