Abstract:
Programs can be optimized at runtime prior to execution to enhance performance. Program instructions/operations designated for execution can be recorded and subsequently optimized at runtime prior to execution, for instance by performing transformations on the instructions. For example, such optimization can remove, reorder, and/or combine instructions, among other things.
Abstract:
Computer programming is aided by way of automatic code generation, and more specifically generation of deployment code automatically. An application can be analyzed and deployment code, including installation, maintenance (e.g., update/upgrade), and removal (e.g., un-install) code, can be generated as a function of the analysis as well as a particular execution environment.
Abstract:
A representation of a language-integrated query can be generated based upon a homomorphism characteristic of the query. The representation can be utilized to enable efficient execution of the query on a key-value store, for example. More specifically, the query can be transformed into a representation utilizing language integrated query operators that enables parallel execution.
Abstract:
Systems and methods are provided with respect to computer programming. Program behavior can be tuned to provide a seamless mixture of semantic behavior across a single program language syntax. Semantic behavior can be explicitly specified at arbitrary levels of syntactic granularity (e.g. expressions, members, types, compilation units . . . ), wherein semantic scope is commensurate with the specified level of granularity.
Abstract:
Program language support is provided to facilitate reactive programming. Code can be provided that initiates conversion between a first-class pattern and a second-class pattern, wherein the patterns operate with respect to push-based data. Support is also provided for producing and consuming push-based data in accordance with an iterator pattern, for example.
Abstract:
A data model can be generated by dualizing another data model. In other words, a first data model can be transformed into a second data model, wherein the second data model is a mathematical dual of the first data model. For example, a non-relational data model can be generated by dualizing a relational data model.
Abstract:
A query over one or more push-based data sources is transformed into a data representation of the query. The data representation can subsequently be analyzed, optimized, and remoted, among other things. For example, the data representation can be utilized to generate code for an out-of-process execution engine. Additionally, the data representation can be employed with respect to conversions to and from various types and representations of data.
Abstract:
Communication symmetry is leveraged to facilitate testing of network services. To identify, isolate, understand, and resolve problems a test client is employed. In accordance with one aspect, a service can be provided for execution on a service consumer while the test client resides on a service provider. Roles are reversed to provide more testing freedom on the provider side and less intrusion on the consumer side. Additionally or alternatively, a service and/or test client can be shipped to consumers to aid testing in a real execution environment.
Abstract:
Dynamic dispatch for classes and interfaces is encapsulated in a class-less scripting language. A plurality of mechanisms is employed to facilitate dynamic polymorphism. One or more target-language constructs, such as dictionary objects, prototype objects and/or derived types, are utilized to capture class and interface-method implementations. These constructs are subsequently referenced at runtime to invoke appropriate code.
Abstract:
A system and method for controlling the execution of notifications in a computer system with multiple notification contexts. A RunOn operator enables context hopping between notification contexts. Push-based stream operators optionally perform error checking to determine if notifications combined into a push-based stream share a common notification context. Context boxes group together notification creators and associate their notifications with a common scheduler and notification context. Operators employ a composition architecture, in which they receive one or more push-based streams and produce a transformed push-based stream that may be further operated upon. Components may be used in combinations to implement various policies, including a strict policy in which all notifications are scheduled in a common execution context, a permissive policy that provides programming flexibility, and a hybrid policy that combines flexibility with error checking.