Fixed Function Pipeline Application Remoting Through A Shader Pipeline Conversion Layer
AssigneeMicrosoft Corporation
InventorsNadim Y. Abdo, Max Alan McMullen
Life of this patent
Estimating the term…
Abstract
Systems, methods and computer readable media are disclosed for sending a client graphics data across a remote session for an application, where the application makes fixed function pipeline API calls and the client and server support shader pipeline API calls for the remote session. fixed function pipeline graphics calls from sent from the application are intercepted, wrapped, converted into their fixed function pipeline equivalent graphics call or calls and then sent across the communications network to the client according to a protocol of the remote session.
Claims20
A method for sending graphics calls for an application that uses a fixed function pipeline application programming interface (API) to a client via a remote session that supports sending shader pipeline API calls, comprising:
- intercepting a fixed function pipeline API call of the application;
- wrapping the fixed function pipeline call;
- mapping the wrapped call to a shader pipeline API call;
- and
- sending the shared pipeline API call to the client.
A system for sending graphics calls for an application that uses a fixed function pipeline application programming interface (API) to a client via a remote session that supports sending shader pipeline API calls, comprising:
- circuitry for intercepting a fixed function pipeline API call of the application;
- circuitry for wrapping the fixed function pipeline call;
- circuitry for mapping the wrapped call to a shader pipeline API call;
- and
- circuitry for sending the shared pipeline API call to the client.
A computer-readable storage medium comprising computer-readable instructions, that when executed on a processor, cause the processor to perform operations comprising:
- intercepting a plurality of fixed function pipeline API calls of an application;
- wrapping each fixed function pipeline call;
- mapping each wrapped call to a shader pipeline API call;
- optimizing the shader pipeline API calls to produce at least one optimized shader pipeline API call;
- and
- sending each optimized shared pipeline API call to the client.
Dependencies are inferred from the claim text.