Microsoft Technology Licensing, LLC

Mark T Anders

Scott David Guthrie

David S Ebbo

Stephen James Millet

Gary Steven Burd

Ted Andrew Peters

Kenneth Bruce Cooper

Manu Vasandani

Erik B Olson

Erik B Christensen

Nikhil Kothari

Stefan Harrington Pharies

Dmitry Robsman

Keith W Ballinger

Anthony J Moore

Yann Christensen

Fabio A Yeon

Susan M Warren

Adam Wade Smith

Robert Michael Howard

Suzanne Maurine Cook

Mark A Boulter

Jayanth V Rajan

Satoshi Nakajima

John Peter Shewchuk

Michael Joseph Toutonghi

Anders Hejlsberg

Gopala Krishna R Kakivaya

Yan Valerie Leshinsky

Christopher Wellington Brumme

Giovanni Moises Della-Libera

Michael M Magruder

Raja Krishnaswamy

David Bau

Brian LaMacchia

Murali R Krishnan

Gregory Darrell Fee

Lance Olson

Henry L Sanders

Julie D Bennett

James S Miller

Travis Muhlestein

Sean Edwin Trowbridge

Seth B Pollack

Jonathan C Hawkins

James E Allard

Krzysztof J Cwalina

Seth Mitchell Demsey

Luca Bolognese

Brian M Grunkemeyer

Shawn Patrick Burke

Christopher L Anderson

Loren Kohnfelder

Yung-Shin Lin

Brian Keith Pepin

Jun Fang

Jeffrey M Cooperstein

James H Hogg

Craig T Sinclair

Corina Eva Feuerstein

Nicholas M Kramer

Alan Geoffrey Boshier

Caleb L Doise

Shajan Dasan

David S Mortenson

Manish S Prabhu

David L Kaplan

Chad W Royal

Radu Rares Palanca

John I McConnell

Tarun Anand

Joseph L Roxe

Ting-Hao Yang

Mark W Fussell

Joe Dennis Long

Sreeram Nivarthi

Jesus Ruiz-Scougall

Hany E Ramadan

Omri Gazitt

Ramasamy Krishnaswamy

Nithyalakshmi Sampathkumar

Daniel Takacs

Daniel Dedu-Constantin

Neetu Rajpal

Joseph Keith Croney

Lei Jin

Blaine J Dockter

William A Adams

Andrew David Sigal

Mark P Ashton

Subhag P Oak

Eric B Olsen

Kenneth B Cooper

Ted A Peters

An application program interface (API) provides a set of functions for application developers who build Web applications on Microsoft Corporation's .NET&#x2122; platform.

Application program interface for network software platform

Computing system and method for allowing plurality of applications written in different programming languages to communicate and request resources or services via a common language runtime layer

A network-based distributed application system is provided in accordance with the present invention for enabling services to be established locally on a client system. The system may include an application and presentation logic, at least a portion of which is interchangeably processed by a server or a client without modification to the portion. The core functionality provided by the application may be preserved between the client and the server wherein improved network performance may provided along with improved offline service capabilities.

System and method providing multi-tier applications architecture

One or more server-side control objects provide server-side processing of postback input received from client-side user interface elements in a request from a client. Such input may include without limitation postback data and postback events generated from a web page on a client and received by a server in an HTTP request. A hierarchy of server-side control objects can cooperate to process the postback input and to generate the resulting authoring language code, such as HTML. Server-side events can also result from the server-side processing of postback input. In addition to processing postback input, server-side processing may include, without limitation, state management of server-side control objects and binding data to and from server-side database. After the processing and generating operations, the server-side control object hierarchy is terminated until a subsequent request is received from the client.

Postback input handling by server-side control objects

Web pages that share a common layout and/or functionality are associated with at least one master page and at least one endpoint page. Each master page specifies a common layout and/or functionality that are intended to be shared between the web pages. The master pages also include content place holders that identify content segments that are intended to be replaced by content that is obtained from the at least one endpoint page. When a client system requests one of the web pages, the server system merges the appropriate master page and endpoint page into a resulting page that can be rendered as the requested web page by the client system. This enables web pages sharing common features to be created automatically, in real-time, and transparently to the client system, and without having to redundantly store duplicative content for each of the web pages at the server system.

Utilizing common layout and functionality of multiple web pages

A server-side control object processes and generates a client-side user interface element for display on a web page. Multiple server-side control objects may be combined into a hierarchy of server-side control objects that cooperate to generate the resulting authoring language code, such as HTML, for display of a web page on a client. The operation of processing the client-side user interface element may include at least one of an event handling operation, a postback data handling operation, a data binding operation, and a state management operation. The state management operation relates to the state of a server-side control object.

Server-side control objects for processing client-side user interface elements

An application program interface includes a first class to provide information regarding a current HTTP request. The application program interface also includes a second class to manage HTTP output to a client and an object to provide access to server-side utilities and processes. Particular application program interfaces include additional classes to manipulate cookies, handle file transfers, provide exception information, or control operation of an output cache.

Application program interface that enables communication for a network software platform

The state of one or more server-side control objects is managed using a transportable state structure that is communicated between a web server and a client. The transportable state structure may include state information, hierarchical information, and an integrity code. Prior to a response to the client, the state information of one or more server-side control objects is recorded into the transportable state structure for transmission to the client in the response. The transportable state structure is then returned to the server and loaded into the server-side control objects to restore the hierarchy to its previous state.

State management of server-side control objects

A method and apparatus to create an intermediate language or source code file from a server-side resource or dynamic web page file. The source code can then be compiled into an executable class allowing for rapid generation of web page control objects that perform server-side functions, including the rendering of client responses. The code generation scheme of the present invention is capable of creating control objects connected in a hierarchy to handle event processing and the setting of attributes to the specific objects.

Server-side code generation from a dynamic web page content file

Server-side control objects corresponding to client-side user interface elements are created in a control object hierarchy. Properties of the control objects may be data bound to properties of a server-side data source (e.g., a server-side database). Hierarchical data binding relationships are established between properties of control objects and properties of a data source. Template declarations are used to define the configuration of binding container objects that correspond to data objects in the data source. An iterating control object determines the number of data objects in the data source increase according number of binding container objects. A simple data binding types include without limitation: (1) unidirectional data binding from the data source to a control object; (2) unidirectional data binding from a control object to the data source; and (3) bidirectional data binding between a control object and the data source.

Databinding using server-side control objects

The state of one or more server-side control objects is managed using a transportable state structure that is communicated between a web server and a client. The transportable state structure may include state information, hierarchical information, and an integrity code. The state information is related to properties of the server-side control objects. The hierarchical information is used by the server to locate an appropriate server-side control object in the hierarchy into which associated state information is to be loaded. The integrity code allows the server to determine whether the transportable state structure was corrupted during the round-trip between the server and the client. Prior to a response to the client, the state information of one or more server-side control objects is recorded into the transportable state structure for transmission to the client in the response. The transportable state structure is then returned to the server and loaded into the server-side control objects to restore the hierarchy to its previous state.

In a computer environment, a new storage and delivery data format for multimedia object sets increases performance and improves the user experience by reducing the transactions needed to retrieve a set of n objects from n to 1. The object data is interleaved with data definition entries identifying respective object data into a data format comprising a single stream for storage and/or delivery. The data format eliminates the need for multiple, asynchronous transactions thus reducing latency in the data transfer process. Moreover, the data format allows for optimization of how the object data is prioritized and interleaved to achieve desired performance objectives upon delivery of the multimedia objects.

Data format for multimedia object storage, retrieval and transfer

Growing community of inventors

Bellevue, WA, United States of America

Mark T Anders