Abstract: Described herein is a system and method for using object references as a data type. In response to a request for an object reference for an object by a consuming application, the object reference is generated by a source application. The object reference comprises a data structure comprising an activation uniform resource identifier for activating the referenced object, information for visually representing the object reference, and, optionally, metadata that describes the referenced object. The generated object reference is provided to an operating system component by the source application which provides the object reference to a consuming application. The consuming application can display information regard the object reference in accordance with the information for visually representing the object reference included in the object reference. The user can request reactivation of the object referenced by the object reference.

Abstract: Described herein is a system and method for using object references as a data type. In response to a request for an object reference for an object by a consuming application, the object reference is generated by a source application. The object reference comprises a data structure comprising an activation uniform resource identifier for activating the referenced object, information for visually representing the object reference, and, optionally, metadata that describes the referenced object. The generated object reference is provided to an operating system component by the source application which provides the object reference to a consuming application. The consuming application can display information regard the object reference in accordance with the information for visually representing the object reference included in the object reference. The user can request reactivation of the object referenced by the object reference.

Abstract: Aspects of the subject matter described herein relate to versioning for databases. In aspects, two or more users may share the same version of data, such as a report, in a database. One of the users may seek to update the data. In response to a request from the user, a new version of the data is created. For data that is not updated via the request, the new version shares data with the previous version, thus saving space. For data this is updated, new segments within the database are created to store the updated data. Each user is allowed to access the data without blocking other users accessing the data.

Abstract: Aspects of the subject matter described herein relate to versioning for databases. In aspects, two or more users may share the same version of data, such as a report, in a database. One of the users may seek to update the data. In response to a request from the user, a new version of the data is created. For data that is not updated via the request, the new version shares data with the previous version, thus saving space. For data this is updated, new segments within the database are created to store the updated data. Each user is allowed to access the data without blocking other users accessing the data.

Abstract: Aspects of the subject matter described herein relate to versioning for databases. In aspects, two or more users may share the same version of data, such as a report, in a database. One of the users may seek to update the data. In response to a request from the user, a new version of the data is created. For data that is not updated via the request, the new version shares data with the previous version, thus saving space. For data this is updated, new segments within the database are created to store the updated data. Each user is allowed to access the data without blocking other users accessing the data.

Abstract: Embodiments are directed to providing schedule-based processing using web service on-demand message handling threads and to managing processing threads based on estimated future workload. In an embodiment, a web service platform receives a message from a client that is specified for schedule-based, background handling. The web service platform includes an on-demand message handling service with processing threads that are configured to perform on-demand message processing. The web service platform loads the on-demand message handling service including the on-demand message handling threads. The web service platform implements the on-demand message handling service's threads to perform background processing on the received client message. The client messages specified for background handling are thus handled as service-initiated on-demand tasks.

Abstract: Embodiments are directed to providing schedule-based processing using web service on-demand message handling threads and to managing processing threads based on estimated future workload. In an embodiment, a web service platform receives a message from a client that is specified for schedule-based, background handling. The web service platform includes an on-demand message handling service with processing threads that are configured to perform on-demand message processing. The web service platform loads the on-demand message handling service including the on-demand message handling threads. The web service platform implements the on-demand message handling service's threads to perform background processing on the received client message. The client messages specified for background handling are thus handled as service-initiated on-demand tasks.

Abstract: Described are embodiments directed to providing a preview feature in a report designer that allows modifications to report metadata to be made and previewed accurately. In embodiments, the feature allows a user to open a report to make changes to metadata of the report and have an accurate preview of how the report will look when published on a report publishing server. Embodiments provide for a report publishing server to allocate an in memory location that stores modified metadata of a report. The in memory location allows relative paths and references to sub-reports or data sources in the original report to be accurately reflected in a preview on the client.

Abstract: Aspects of the subject matter described herein relate to versioning for databases. In aspects, two or more users may share the same version of data, such as a report, in a database. One of the users may seek to update the data. In response to a request from the user, a new version of the data is created. For data that is not updated via the request, the new version shares data with the previous version, thus saving space. For data this is updated, new segments within the database are created to store the updated data. Each user is allowed to access the data without blocking other users accessing the data.