Andrew Richard Sterland

8290152, Oct 16, 2012

Aug 30, 2007

11/897381

John I. Montgomery - Seattle WA, US
Adam D. Nathan - Redmond WA, US
Timothy Rice - Bellevue WA, US
Andrew Sterland - Redmond WA, US

Microsoft Corporation - Redmond WA

H04L 9/00
H04L 9/08
H04L 29/06
H04L 9/32
G06F 7/04
G06F 15/16
G06F 17/30
G06F 11/30
G06F 12/14

380 44, 380281, 380284, 726 4, 726 6, 713171, 713189

Various technologies and techniques are disclosed for managing web service developer keys. A generic key identifier can be generated based on an original web service key. The generic key identifier is used within source code of an application being developed. Upon receiving a request to run the application, the generic key identifier is transformed back into the original web service key prior to calling an associated web service. Multiple users can securely share the same application that uses the web service. When one user who does not have his own original web service key accesses the application, that user can be prompted to obtain and enter the original web service key once the key has been obtained from a provider of the web service.

8539506, Sep 17, 2013

Feb 9, 2012

13/370126

Michael C. Fanning - Redmond WA, US
Christopher M. H. Faucon - Redmond WA, US
Andrew R. Sterland - Seattle WA, US
Timothy S. Rice - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 13/00

719313, 719328, 717111

Techniques are described herein that are capable of dynamically injecting code into a running process. For instance, the techniques are capable of causing arbitrary code to be activated in the process while the process is running in response to receipt of a request for dynamic execution of the arbitrary code from outside the process while the process is running.

8543638, Sep 24, 2013

Sep 24, 2007

11/903598

Adam D. Nathan - Redmond WA, US
Andrew Sterland - Redmond WA, US
Michael J. Leonard - Lake Stevens WA, US
Timothy Rice - Bellevue WA, US
John I. Montgomery - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 15/16

709203, 709204, 709205

Various technologies and techniques are disclosed for enhancing security in a browser-based environment. A first browser application hosts one or more other applications. The first browser application is operable to load the one or more other applications on one or more separate domains than a host domain, using one or more cookies as a communication method between the first browser application and the one or more other applications. Input is received from a user to access a first browser application on a first domain. A selection is received from the user to run a second browser application from within the first browser application. A first cookie is created in a second domain, with the first cookie containing information to be used by the second browser application. The second browser application is loaded on the second domain. For example, the first browser application can be a browser-based software development application.

20090288065, Nov 19, 2009

May 16, 2008

12/121984

Adam D. Nathan - Redmond WA, US
Andrew R. Sterland - Seattle WA, US
Timothy S. Rice - Bellevue WA, US
Michael J. Leonard - Lake Stevens WA, US
John I. Montgomery - Seattle WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 9/44

717107

Described is a technology in a programming (development and/or runtime) environment by which data type mismatches between the output and input of computer program software components (e.g., APIs) are detected, with the output transparently converted such that the converted input may be understood by the inputting component. When components are interconnected in a programming environment, metadata associated with those components is evaluated to determine a type mismatch, e.g., between objects and arrays. If mismatched, an output object is converted to a single-element array for input, or alternatively, an output array is converted to a series of objects, each object sent within a loop for input. The transparent conversion may be performed by the programming environment during runtime, or by inserting conversion code prior to compilation.

20090288067, Nov 19, 2009

May 16, 2008

12/122021

Adam D. Nathan - Redmond WA, US
Andrew R. Sterland - Seattle WA, US
Timothy S. Rice - Bellevue WA, US
Michael J. Leonard - Lake Stevens WA, US
John I. Montgomery - Seattle WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 9/44

717114

Described is a technology by which metadata augments a programming language such as JavaScript. Software components such as application programming interfaces are associated with metadata. When a software component is selected for use, such as when putting together a computer program in a graphical programming environment, its corresponding metadata is accessed. The metadata may be used to validate the usage of the software component, such as to validate a constraint associated with a value, provide a default value, validate a value's type, and/or determine whether a value is required. Validation may also determine whether data output by one software component is of a type that is appropriate for input by another software component. In addition to validation via type metadata, the metadata may provide descriptive information about the selected software component, such as to assist the programmer and/or provide further information to the programming environment.

20090293059, Nov 26, 2009

May 20, 2008

12/123473

Adam D. Nathan - Redmond WA, US
Andrew Sterland - Seattle WA, US
Michael J. Leonard - Lake Stevens WA, US
Timothy S. Rice - Bellevue WA, US
John I. Montgomery - Seattle WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 9/46

718100

A workflow design system receives a set of parameters that are to be used in a workflow, as well as an indication of a function that is to be performed in the workflow. The workflow design system uses a mapping component to map the parameters to inputs of the identified function. The workflow design system then outputs suggested mappings of the parameters to the function inputs, and optionally waits for user confirmation. Once user confirmation is received (if it is required), either the workflow design system or the mapping component automatically generates the connections between the parameters and the function inputs.

20090293073, Nov 26, 2009

May 20, 2008

12/123472

Adam D. Nathan - Redmond WA, US
Andrew Sterland - Seattle WA, US
Michael J. Leonard - Lake Stevens WA, US
Timothy Rice - Bellevue WA, US
John I. Montgomery - Seattle WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 9/46

719328

Various technologies and techniques are disclosed for automating asynchronous programming in single threaded systems. A wrapper is automatically generated around an original function. When metadata indicates the wrapper should be utilized for asynchronous data retrieval, the wrapper calls a data retrieving function asynchronously. Asynchronous retrieval of data is initiated from the data retrieving function using a direct callback. A specially marked exception is thrown to cause control to leave and get caught by a special exception in the wrapper. When the direct callback function is called because the data has been retrieved, the data is saved. The wrapper is called again in a synchronous fashion, which causes the wrapper, original function, and data retrieving function to be called again. When the data retrieving function is called again, data that was saved by the direct callback function is retrieved, and then returned to the calling function through the callback function.

20100125623, May 20, 2010

Nov 18, 2008

12/273516

Timothy S. Rice - Bellevue WA, US
Andrew R. Sterland - Seattle WA, US
Patrick Chi Wai Wong - Bellevue WA, US
Adam D. Nathan - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 15/16

709202

A system and method is described for communicating requests from a Web mashup being executed within the context of a Web browser to third-party Web services in a manner that does not violate the Same Origin Policy (SOP) observed by many Web browsers. In one embodiment, a workflow engine operating in the context of a Web browser executes a plurality of executable components comprising a Web mashup. The workflow engine transparently redirects Web service requests generated by the executing components to a proxy server that acts as an intermediate between the workflow engine and third-party Web services. The proxy server, which is not subject to SOP, transmits the Web service requests to the third-party Web service and obtains requested data therefrom. The proxy server further returns the requested data in a manner that is useable by the Web mashup components.