Microsoft Technology Licensing, LLC

Hewlett-packard Development Company, L.p.

Eric Wendell Johnson

Jan Stephen Gray

Craig Henry Wittenberg

Satish Ramchandra Thatte

Richard Douglas Hill

James M Lyon

Gopal Krishna R Kakivaya

Rebecca Ann Norlander

Scott G Robinson

Ajay K Gummadi

Christopher Wellington Brumme

Michael Joseph Toutonghi

Alan Aitken Ramaley

Neelamadhaba Mahapatro

Richard J Lamoreaux

Jeremy Dinsel

Matthew Von Bargen

Network automation systems, and methods of implementing planned changes to a network infrastructure are provided. A network automation system includes software configured to model a manual change of the planned change and identify a conflict between the manual change and another change of the planned change. The system also includes a policy module configured to verify that the changes of the planned change conform to a policy. The system further includes a device proxy configured to allow a user to implement the manual change. An exemplary method for implementing the planned changes includes modeling a manual change of the planned change, checking for a conflict between the manual change and another change, and implementing the planned change. The method can also include verifying that the manual change complies with a policy.

Methods for managing manual changes to network infrastructures through automated systems

A system and method for managing access control lists on network devices is provided. One or more access control lists are retrieved from one or more computing devices. The one or more access control lists are stored. A request to update the one or more access control lists is received. The one or more access control lists are automatically updated based on the request. The updated one or more access control lists are then deployed to the one or more computing devices.

System and method for managing the application of access control lists on network devices

Communication among agile objects and context-bound objects within object-oriented programming environments, including communication across contextual boundaries, is disclosed. In one embodiment, a reference to a second object within a second context is wrapped in a proxy wrapper. A first object within a first context calls the second object via the wrapped reference. No direct reference is held by the first object to the second object. Other embodiments relate to agile objects. Agile objects called by context-bound objects execute in the contexts of their callers. The context of a calling context-bound object becomes the context of an agile object for calling of the agile object by the calling context-bound object. Direct reference to the agile object by the context-bound object is thus permitted.

Communication among agile and context-bound objects

An object system provides composable object execution environment extensions with an object model that defines a framework with contexts, policies, policy makers and activators that act as object creation-time, reference creation-time and call-time event sinks to provide processing of effects specific to the environment extensions. At object creation time, an object instantiation service of the object system delegates to the activators to establish a context in which the object is created. The context contains context properties that represent particular of the composable environment extensions in which the object is to execute. The context properties also can act as policy makers that contribute policies to an optimized policy set for references that cross context boundaries. The policies in such optimized sets are issued policy events on calls across the context boundary to process effects of switching between the environment extensions of the two contexts.

Environment extensibility and automatic services for component applications using contexts, policies and activators

A method and system for editing actual work records with a start date, an end date and a work value. A period actual is entered, including a period actual start date, period actual end date, and a period actual work value. Before the period actual is stored as an actual work record, it is determined whether there is any overlap between the actual work records and the period actual. If so, any overlap between the actual work records and period actual is eliminated. Any overlapping actual work records that are completely within the period actual, i.e., with a start date and end date between the period actual start date and period actual end date, are deleted. For an overlapping actual work record that surrounds the period actual, i.e., the period actual start date and period actual end date are between the start date and end date, the end date and work value of the overlapping actual work record are modified and a new actual work record is created. For an overlapping period actual with a start date before the period actual end date and an end date equal to or between the period actual start date and period actual end date, the end date and work value are modified. For an overlapping period actual with a start date equal to or between the period actual start date and period actual end date and an end date after the period actual end date, the start date and work value are modified.

Method and system for editing actual work records

Centrally handling a runtime error or exception of a program using a central object stack and exception handling code centrally maintained within a global object manager. The global object manager is a data structure separate from the program's call stack. When a modified TRY statement is executed, a location is marked on the central object stack. During execution of a section of code after the modified TRY statement, if a new object is needed, the global object manager efficiently allocates the new object. The global object manager either allocates the new object directly from memory or attempts to re-use a previously allocated object in a cache of available objects as the new object. The new object is then registered on the central object stack and a pointer to the new object is registered on the program's call stack. This keeps the new object and associated exception handling code off the program's call stack. When an exception is thrown, the global object manager cleans up and unregisters an object which was registered on the central object stack since the marked location. If a re-use condition is met, the object is kept in the cache as an available object already allocated from memory. However, if the re-use condition is not met, the object is de-allocated from memory.

System and method for centrally handling runtime errors

Growing community of inventors

Redmond, WA, United States of America

Eric Wendell Johnson