Microsoft Technology Licensing, LLC

Eric Kenneth Zinda

Stephen James Millet

Stephen T Swartz

David Wortendyke

Lance Olson

Erik B Olson

Michael Marucheck

Michael Steven Vernal

Jennifer Ruth Mead

Ryan Thomas Sturgell

Daniel J Fisher

Malti Raghavan

James Jubak

Jesus Ruiz Scougall

Alex DeJarnett

Erik B Christensen

Stephen Michael Danton

Kenneth David Wolf

Giovanni Moises Della-Libera

C Douglas Hodges

John Raymond Justice

Stefan Harrington Pharies

Christopher L Anderson

Craig Andrew Critchley

Uday Sooryakant Hegde

Elliot Lee Waingold

Tomasz Janczuk

Shy Cohen

Noaa Avital

Brian Robert Marshall

William Edwin Hiebert

Gersh Payzer

Pedro Ardila

David C Johnson

Yaniv Pessach

Zhenglei Pan

User experience in a designer tool manages cogeneration of a database application and a database accessible through the application. A user places a visual representation of an application element designed to control a relational or hierarchical dataset. Code is automatically called to add the application element to the application, and automatically invoked to create database schema elements designed to implement the dataset in the database under application element control. Users verify that an application element has been automatically added, and confirm that database schema elements implementing the dataset(s) under control of the application element have been automatically created. A tutorial illustrates a workflow utilizing a designer tool to cogenerate a database application and a database without a data design step. A wizard utilizes the designer tool to cogenerate a database application and a database that collectively implement a calendar, a diagram, a tree, a wiki, and/or a list.

Cogeneration of database applications and their databases

A system and method provides investors with meaningful information extracted from large volumes of available data for a particular stock, mutual fund, bond, or other investment. The system includes one or more computers that receive and process multiple data feeds to extract information relating to each type of investment. The processed data is compared to 'alert rules' each corresponding to a predefined condition, and a truth table is established that identifies alerts that are true for each particular investment. An investor logs onto a web site and enters a stock ticker symbol or similar investment identifier. Computer software displays a web page including 'alerts' that are presently true for that particular investment. The alerts can be predefined by financial experts to make them useful to novice investors. When an investor selects a particular investment, a display is generated showing all of the alerts that are true for that investment and allowing the user to get more information concerning the significance of the alerts. The alerts can be grouped into different categories according to their content or time sensitivity.

Automated investment alerts from multiple data sources

The present invention extends utilizing abstract descriptions to generate, exchange, and configure service and client runtimes. A computer system parses compiled code and potentially optional configuration information for implementing a service and converts the compiled code and any configuration information into an abstract service description. The abstract service description can then be converted into code document object model and service configuration information or exported as metadata. A corresponding service runtime can be initiated by calling a service initializer included in the abstract service description. The code document object model and configuration information and/or metadata can be transferred to another computer system. The other computer system can utilize the code document object model and configuration information and/or import the metadata to facilitate initialization of a compatible channel for communicating with the service runtime.

Utilizing abstract descriptions to generate, exchange, and configure service and client runtimes

The present invention provides for an automated, user friendly way of constructing and using a binding object. A developer is presented with and selects binding elements that will ultimately be used to create a runtime communication channel for transporting a message between a client and service endpoint. After receiving the user input, metadata, a channel factory and listener factory are created. The metadata describes binding elements and provides an abstract representation of a protocol stack that implements communication aspects at runtime. The channel factory is configured to use the collection of metadata at runtime to generate the runtime communication channel. Further, the listener factory is configured to accept the runtime communication channel for de-multiplexing the communication aspects in order to process the message at a service endpoint. The present invention also provides for groupings of binding elements and standardized binding objects organized based on industry need.

System and method for building and using communication binding objects

System and method for providing automated investment alerts from multiple data sources

Communication channels are partitioned among active nodes in an unbounded computing space. A node may register with a discovery system to obtain an address window (that may correspond to a range of IP addresses). The node communicates only with nodes in accordance with the address window. Even though a partition corresponds to a subset of the nodes in the unbounded computing space, the partition overlaps with partitions of other nodes so that all nodes may interact with each other, either directly or indirectly. Because a node may be cognizant of a small subset of active nodes in the unbounded computing space, both security and scalability are supported.

Peer communication channel partitioning

A method and system for preventing undesired behaviors by executable code modules in a peer-to-peer computer system are provided. When a code module is received, an assembly inspection module queries a blacklist for the received code module. When the received code module is found on the blacklist, the computer system prevents execution of the received code module. Each peer includes an assembly inspection module. When the received code module is not found on the blacklist, the assembly inspection module inspects the received executable code module, prior to execution, to determine whether the code module can perform any undesired behaviors. If so, the received code module is added to the blacklist and prevented from executing.

Peer assembly inspection

The present invention extends to mapping between object oriented and service oriented representations of a distributed application. A computer system accesses an annotated object oriented representation of a service, which is annotated with service description attributes mapping included objects to corresponding service oriented elements in a service oriented representation of the service. The computer system identifies a service description attribute that annotates an object of the annotated object oriented representation. The computer system maps the object to a corresponding service oriented element in accordance with service description information contained in the identified service description attribute. The computer system outputs a channel object configured to implements behaviors and data formats described in the service oriented representations. The computer system initiates a channel that is compatible with behaviors and data formats of the service.

Mapping between object oriented and service oriented representations of a distributed application

In a distributed computing architecture, a method and system for authenticating a message as originating from an unaltered or unmodified node is provided. Prior to sending a messages, a black box software module in a node validates the node to determine whether the node has been altered or modified without authorization. Once validated, the black box alters a message, using a black box protection scheme, in such a manner that the message can be subsequently authenticated. The black box module sends the altered message to a peer node, whose own black box authenticates the message using an authentication scheme corresponding to the protection scheme. Because validation is performed, each node may assume that the message originated from an unaltered node. The protection and/or validation scheme can be changed in regular intervals so that attackers do not have time to reverse engineer the black box. Alternatively, validation may be skipped and the key used to alter/protect each message may be based on the environment of the node performing the alteration/protection, so that nodes that have been altered will generate different keys than unaltered nodes, and will not be able to communicate.

Prevention of software tampering

An unbounded computing space including independent nodes is provided. Each node includes a discovery module to detect other nodes within the unbounded computing space, and an interaction module to communicate with the other detected nodes. Any node within the unbounded computing space can introduce an independent agent (e.g., an executable code assembly) into the unbounded computing space. The node in which an independent agent is introduced can subsequently send the independent agent to another node in the unbounded computing space for execution in the other node. Nodes in which an independent agent is introduced can define privileges that are associated with one or more agents and can be used to ensure the agent does not exceed a security policy as defined by the node. This allows for a distributed computing system in which an unlimited number of different agents can be introduced.

Unbounded computing space

A method and apparatus for allowing multiple developers of software applications working in client/server computing network to remotely save, test and debug project files such as web pages. The client computer is capable of emulating server side operations to allow the developer to locally test changes to project files before they are saved on the server. The client computer maintains an accurate view of the overall project, but without having to locally copy the entire software project, by storing file information relating to the software project including, for example, metadata, link information, and BOT replacements, and/or a directory structure of the files and folders in the software project that mirrors the directory structure of the software project on the server. Various features include providing developers with the ability to check out, modify and debug files concurrently with other developers, and merging changes made by different developers to the same file. Concurrently modified files may be merged by prompting a developer when conflicts arise between the files to be merged.

Web developer isolation techniques

Growing community of inventors

Seattle, WA, United States of America

Eric Kenneth Zinda