Microsoft Technology Licensing, LLC

Lawrence William Osterman

Elliot H Omiya

Tassaduq Basu

Wei Zeng

Martyn S Lovell

Mahesh Prakriya

Stephen C Rowe

Robert Albert Wlodarczyk

Michael Aksionkin

Shakeel Solkar

Neeraj Wadhwa

Brent Rector

Harold L Pierson, Iii

Jerry Jay Dunietz

Ales Holecek

Harold Pierson

William J Bolosky

Reed L Townsend

Robert P Fitzgerald

Stephen Harry Wright

Kenneth W Sykes

Frank Dominic Yerrace

Hirofumi Yamamoto

William Robert Messmer

Bharat Shah

Noel Richard Cross

Jacob Rossi

Ivan Medvedev

Aaron Lahman

Krishnan Menon

Raju Ramanathan

Alan Stephenson

Hart Wilson

Benjamin Kuhn

Pak Kiu Chung

Adam Shostack

Joaquin Guanter Gonzalbez

Adeel A Aslam

Technologies for a contract platform versioned according to the set of API contracts provided. API contracts are both development-time and run-time executable components. Each such contract defines a particular set of APIs that are fully supported at run-time by a corresponding implementation module. Contract applications are written to API contracts as opposed to the monolithic APIs of a legacy platform. Such applications are 'platform agnostic'.

API versioning independent of product releases

Systems and methods for managing the lifecycle of an API over a number of different versions of an operating system&#x2014;as well as over a number of different platforms are disclosed. In one embodiment, a method is disclosed wherein for a given API, metadata is created and associated with certain constructs of the API. The metadata may comprise a version indication. A set of versioning rules may be defined. Such versioning rules govern whether a particular construct of an API may be changed for a given version. These versioning rules may be enforced at the time of constructing a new build. The versioning rules may be enforced by the IDE system.

API lifecycle platform and version management

In one embodiment, a unified pointer messagemay describe in a single type of pointer message a coordinate input from a user via multiple types of pointer devices. An input device interfacemay receive a coordinate inputfrom an input device. A processormay execute an application programming interface layerthat creates a unified pointer messagefor the coordinate input. The processormay send the unified pointer messageto an application. The processormay process a device specific data setunhandled by the application.

Device specific data in a unified pointer message

Information about the operating system application programming interfaces is stored in a known format in a known location. This information fully describes the APIs exposed by the operating system and is stored in API metadata files. A language compiler or interpreter uses this API information to build a natural and familiar representation of the native system API in the target language. The language compiler or interpreter can read the API information at compile time and/or runtime. The metadata is used to allow an application to refer to named elements in the API. Projections are built that use the metadata to map named elements in the API to named elements in the target language, and to define wrappers that marshal data of those elements between the target representation and the native operating system representation.

Projecting native application programming interfaces of an operating system into other programming languages

Various embodiments provide an ability to abstract type resolution between multiple type systems. At least one type can be described in one or more programmatically accessible file(s). In some embodiments, an application using a different type system can programmatically access and resolve a type of the at least one type system without knowledge of a location of where a description of the type resides. Alternately or additionally, type descriptions contained in the one or more programmatically accessible file(s) can be analyzed and restructured into one or more new programmatically accessible file(s) based, at least in part, upon the type descriptions.

Flexible metadata composition

Evaluating a threat model for structural validity and descriptive completeness. A threat modeling application provides a progress factor or other overall score associated with the structural validity and descriptive completeness of the threat model being evaluated. The structural validity is evaluated based on a data flow diagram associated with the threat model. The descriptive completeness is evaluated by reviewing descriptions of threat types in the threat model. The progress factor encourages modelers to provide effective models to a model reviewer, thus saving time for the model reviewer.

Evaluating the effectiveness of a threat model

Interface identifier parameterization techniques are described. In one or more implementations, a textual description is obtained of a parametric type represented in a binary standard of a programming model and an interface identifier is generated based at least in part on the obtained textual description of the parametric type.

Parameterized interface identifier techniques

Described herein are one or more implementations offering a centralized (e.g., single-point) user-interface, where a user may manipulate audio properties (e.g., volume level) for one or more audio submixes produced by each of multiple active operating-system processes.

Audio submix management

Various embodiments provide techniques for allowing an application to opt out of system default audio stream behavior, as well as techniques for notifying applications on a computing device that a communication audio stream has been initiated. The techniques may differentiate between communication-related audio streams and audio streams that are not communication-related. In some embodiments, an application may register to receive notification that a communication stream has been initiated. The application may be configured to comply with system default audio stream handling policies, or it can perform custom behavior in response to the audio stream notification. In some embodiments, an application may register for filtered or unfiltered notification. In a filtered notification scenario, an application is notified that a communication stream has been initiated when an audio stream associated with the application has not already been modified in response to the initiation of a different communication stream. In an unfiltered notification scenario, an application/process is notified whenever a communication stream is been initiated.

Audio stream notification and processing

A computer-implemented method uses out-of-band notifications to reduce overhead associated with notifying a client process of events that have occurred at a server process in a computer system employing a request-response protocol. Initially, a notification transmission connection is established between the client process and the server process using the request-response protocol. Thereafter, notifications are transmitted from the client process to the server process using the connection, and without using the request-response protocol to transmit the notifications.

Distributed notification

A computer-implemented method uses out-of-band data transmission to reduce overhead associated with data transmission between a client process and a server process in a computer system employing a request-response protocol. Initially, a data transmission connection is established between the client process and the server process using the request-response protocol. Thereafter, data is transmitted between the client process and the server process using the connection, and without using the request-response protocol to transmit the data.

Out-of-band data transmission

A computer-implemented method selects a desired copy of a particular interface in a computer system that includes a client computer and a server computer. The method includes, at the server computer, annotating the desired copy of the interface with an identifier, and, at the client computer, selecting the desired copy of the interface based on the associated identifier. The annotating and selecting steps may be implemented using the RPC protocol.

Method and system for accessing a particular instantiation of a server

Growing community of inventors

Woodinville, WA, United States of America

Lawrence William Osterman