Patents by Inventor Bruce Payette
Bruce Payette has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).
-
Patent number: 8850414Abstract: Method and system for direct access of language metadata are disclosed. In an implementation, the method includes receiving commands from a user to modify language metadata of a programming language. The metadata is modified based on the command and the modified metadata is utilized as a feature in the programming language at runtime.Type: GrantFiled: February 2, 2007Date of Patent: September 30, 2014Assignee: Microsoft CorporationInventors: Bruce Payette, George Xie, Jonathan M. Rowlett, Lee Holmes, Jeffrey P. Snover, Jim Truher
-
Patent number: 8332509Abstract: A computer monitoring system uses a set of parameterized models to gather information about monitored devices. The models include scripts for gathering information, as well as type validation and data validation functions. The parameters within the model are used to generate user interface prompts and to populate discovery scripts as well as data validation scripts. In some cases, the models may include localization settings that may customize the user interface and validation output for different languages. A processing engine may generate a user interface from the parameters defined in the models, customize the scripts from the user input, and cause the scripts to be executed. The data gathered by the scripts may be analyzed using type validation and data validation.Type: GrantFiled: February 20, 2010Date of Patent: December 11, 2012Assignee: Microsoft CorporationInventors: James Robertson, Jeffrey Snover, Sameer Mutatkar, Rahim Maknojia, Christine Moeller, Bruce Payette
-
Publication number: 20110208855Abstract: A computer monitoring system uses a set of parameterized models to gather information about monitored devices. The models include scripts for gathering information, as well as type validation and data validation functions. The parameters within the model are used to generate user interface prompts and to populate discovery scripts as well as data validation scripts. In some cases, the models may include localization settings that may customize the user interface and validation output for different languages. A processing engine may generate a user interface from the parameters defined in the models, customize the scripts from the user input, and cause the scripts to be executed. The data gathered by the scripts may be analyzed using type validation and data validation.Type: ApplicationFiled: February 20, 2010Publication date: August 25, 2011Applicant: MICROSOFT CORPORATIONInventors: James Robertson, Jeffrey Snover, Sameer Mutatkar, Rahim Maknojia, Christine Moeller, Bruce Payette
-
Publication number: 20080189683Abstract: Method and system for direct access of language metadata are disclosed. In an implementation, the method includes receiving commands from a user to modify language metadata of a programming language. The metadata is modified based on the command and the modified metadata is utilized as a feature in the programming language at runtime.Type: ApplicationFiled: February 2, 2007Publication date: August 7, 2008Applicant: Microsoft CorporationInventors: Bruce Payette, George Xie, Jonathan M. Rowlett, Lee Holmes, Jeffrey P. Snover, Jim Truher
-
Publication number: 20070180531Abstract: Computerized facilitation of an assessment of risk associated with running interpretable code. The interpretable code under evaluation is parsed to identify a command unit within the interpretable code. One or more risk factors associated with the identified command unit is then identified using the parsed code. A report is then made of including identification of the command unit found the interpretable code along with the identified associated one or more risk factors. Thus, a user need not have to read and evaluate the interpretable code itself, but may instead review the much less complex report to evaluate the risks associated with running the interpretable code.Type: ApplicationFiled: January 25, 2006Publication date: August 2, 2007Inventors: Jeffrey Snover, Bruce Payette
-
Publication number: 20070174821Abstract: The adaptation of at least a portion of an object provided by a previous script component to a subsequent script component, despite the subsequent component being incapable of recognizing a format of the at least a portion of the object as provided by the previous component. The previous component generates an object having a property. Adaptation script identifies adaptation(s) to perform on the property prior to being used by the subsequent component. The adaptation is performed, and the adapted property is then used by the subsequent component.Type: ApplicationFiled: January 25, 2006Publication date: July 26, 2007Applicant: Microsoft CorporationInventors: Jeffrey Snover, Bruce Payette, Jeffrey Jones, Kenneth Hansen
-
Publication number: 20070174813Abstract: Script is accessed and interpreted to identify an executable component. Processing context configuration files may then be used to identify an appropriate processing context for the identified executable component. Examples of processing context include, but are not limited to, a process in which the identified executable component is to run, one or more adaptations to perform on the component prior to running, and/or a security context in which to run the component. Processing context thus need not be specified in the actual script itself. The identified components may then be executed in the identified processing context.Type: ApplicationFiled: January 25, 2006Publication date: July 26, 2007Applicant: Microsoft CorporationInventors: Jeffrey Snover, Bruce Payette, Dana Huang
-
Publication number: 20070135949Abstract: In an administrative tool environment, user input is supplied to an administrative tool framework for processing. The administrative tool framework maps user input to cmdlet objects. The cmdlet objects describe a grammar for parsing the user input and input objects to obtain expected input parameters. The input objects are emitted by one cmdlet and are available as input to another cmdlet. The input objects may be any precisely parseable input, such as .NET objects, plain strings, XML documents, and the like. The input objects are not live objects. The cmdlets may operate within the same process. Alternatively, one cmdlet may operate locally while another cmdlet operates remotely. The cmdlets may be provided by the administrative tool framework or may be provided by third party developers. The user input may be supplied to the framework via a host cmdlet.Type: ApplicationFiled: February 23, 2007Publication date: June 14, 2007Applicant: MICROSOFT CORPORATIONInventors: Jeffrey Snover, Daryl Wray, James Truher, Bruce Payette
-
Publication number: 20070028211Abstract: The techniques and mechanisms described herein are directed to an interpreter security mechanism that minimizes security risks associated with interpreting a script written with a scripting language. The interpreter security mechanism recognizes a marker that indicates a beginning for a set of non-interpreted lines. Upon recognizing the marker, the interpreter refrains from interpreting subsequent lines in the script until an end of marker occurs or an end of file occurs. The end of marker indicates that the interpreter can resume interpreting the lines in the script that follow the end of marker.Type: ApplicationFiled: July 29, 2005Publication date: February 1, 2007Applicant: Microsoft CorporationInventors: Bhalchandra Pandit, Bruce Payette, James Truher, Jeffrey Snover
-
Publication number: 20060277604Abstract: The techniques and mechanisms described herein are directed to a taint mechanism. An object-based command declares a taint directive for a parameter within a command declaration. The taint directive is then associated with that parameter in a manner such that when an engine processes the command, the engine determines whether to process the command based on the taint directive and input for the parameter. The taint directive may specify that the input may be tainted or untainted. The command declaration may also include a taint parameter that specifies a taint characteristic for output from the command. The taint characteristic may be tainted, untainted, or propagated. Any type of object may become tainted. An untaint process may be applied to tainted data to obtain untainted data if an authorization check performed by the engine is successful.Type: ApplicationFiled: May 20, 2005Publication date: December 7, 2006Applicant: Microsoft CorporationInventors: Bhalchandra Pandit, James Truher, Jeffrey Snover, Bruce Payette
-
Publication number: 20060225036Abstract: The techniques and mechanisms described herein are directed to a scripting security mechanism that minimizes security risks associated with interpreting a script written with a scripting language. An interpreter recognizes the scripting-language syntax within the script and processes each line that is designated within a data block using a restrictive set of operations. The restrictive set of operations are a subset of the total operations available for processing. If one of the lines within the data block attempts to perform an operation that is not within the restrictive set of operations, the interpreter provides an indication, such as an exception or message explaining the illegal operation. The interpreter also recognizes a list of export variables associated with the data block and exports only the variables identified in the list to an external environment if the export variable meets a constraint identified for it, if any.Type: ApplicationFiled: March 31, 2005Publication date: October 5, 2006Applicant: Microsoft CorporationInventors: Bhalchandra Pandit, Bruce Payette, James Truher, Jeffrey Snover
-
Publication number: 20060064672Abstract: The techniques and mechanisms described herein are directed at converting text into objects based on a template that describes the format of the text. The objects then being available for further processing. The conversion mechanism converts the text into an object having at least one method that is directly invocable and that is specific to a data type specified for the live object. The template comprises an object header indicator and a corresponding object header pattern. A new object is created whenever the object header pattern is identified within the text. In addition, the template comprises one or more field indicators each having a corresponding field pattern. The field pattern is in a format of a regular expression. A new field is created for the new object whenever a field pattern is identified within the text.Type: ApplicationFiled: September 17, 2004Publication date: March 23, 2006Applicant: Microsoft CorporationInventors: Bhalchandra Pandit, Bruce Payette, James Truher
-
Publication number: 20060064668Abstract: The techniques and mechanisms described herein are directed at converting text into objects based on a template that describes the format of the text, where the format of the text is not in a standardized format. The objects then being available for further processing. The conversion mechanism converts the text into a dead object. The template comprises an object header indicator and a corresponding object header pattern. A new object is created based on the object header pattern identified within the text. In addition, the template comprises one or more field indicators each having a corresponding field pattern. The field pattern may be in a format of a regular expression. A field type and associated value are created from a string associated with the field pattern.Type: ApplicationFiled: November 29, 2004Publication date: March 23, 2006Applicant: Microsoft CorporationInventors: Bhalchandra Pandit, Bruce Payette, James Truher
-
Publication number: 20050091258Abstract: In an administrative tool environment, user input is supplied to an administrative tool framework for processing. The administrative tool framework maps user input to cmdlet objects. The cmdlet objects describe a grammar for parsing the user input and input objects to obtain expected input parameters. The input objects are emitted by one cmdlet and are available as input to another cmdlet. The input objects may be any precisely parseable input, such as .NET objects, plain strings, XML documents, and the like. The input objects are not live objects. The cmdlets may operate within the same process. Alternatively, one cmdlet may operate locally while another cmdlet operates remotely. The cmdlets may be provided by the administrative tool framework or may be provided by third party developers. The user input may be supplied to the framework via a host cmdlet.Type: ApplicationFiled: June 30, 2004Publication date: April 28, 2005Applicant: Microsoft CorporationInventors: Jeffrey Snover, Daryl Wray, James Truher, Bruce Payette
-
Publication number: 20050091201Abstract: In an administrative tool environment, user input is supplied to an administrative tool framework for processing. The administrative tool framework maps user input to cmdlet objects. The cmdlet objects describe a grammar for parsing the user input and input objects to obtain expected input parameters. The input objects are emitted by one cmdlet and are available as input to another cmdlet. The input objects may be any precisely parseable input, such as .NET objects, plain strings, XML documents, and the like. The cmdlets may operate within the same process. Alternatively, one cmdlet may operate locally while another cmdlet operates remotely. The cmdlets may be provided by the administrative tool framework or may be provided by third party developers. The user input may be supplied to the framework via a host cmdlet.Type: ApplicationFiled: October 24, 2003Publication date: April 28, 2005Inventors: Jeffrey Snover, Daryl Wray, James Truher, Bruce Payette