Versions and workspaces in Microsoft repository

Bergstraesser, Thomas; Bernstein, Philip A.; Pal, Somnath; Shutt, David

doi:10.1145/304181.304248

Cited by 6 publications

(3 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although these techniques deal with changing the database schema, they focus on managing change within live databases rather than tracking change during the development process. For example, the Microsoft Repository supports versioning in an SQL Server database (Bergstraesser et al, 1999) with some performance and storage costs. Similar approaches have been applied in object database systems that must persist data objects and also manage different versions of those objects as the code changes (Sciore, 1994;db4objects Inc., 2008).…”

Section: Related Workmentioning

confidence: 99%

DATABASE VERSION CONTROL - A Software Configuration Management Approach to Database Version Control

Kearney¹,

Lepinioti²

2008

Proceedings of the Third International Conference on Software and Data Technologies Special Session on Applications in Banking

View full text Add to dashboard Cite

This paper introduces a database configuration management tool, called DBVersion, that provides database developers with many of the benefits of source code control systems and integrates with software configuration tools such as Subversion. While there has been a lot of research in software configuration management and source code control, little of the work has investigated database configuration issues. DBVersion's main contribution is to allow database developers to use working practices such as version control, branching and concurrent working that have proved successful in traditional software development.

show abstract

Section: Related Workmentioning

confidence: 99%

DATABASE VERSION CONTROL - A Software Configuration Management Approach to Database Version Control

Kearney¹,

Lepinioti²

2008

Proceedings of the Third International Conference on Software and Data Technologies Special Session on Applications in Banking

View full text Add to dashboard Cite

show abstract

“…Only recently has this feature been exploited in distributed computing systems such as COM [BBPS99]. While CORBA has long specified a major and minor version numbers for specifying creation of an object, this service is employed by programmers to keep track of object implementations, rather than to provide substitutability of references of one COBRA object for another.…”

Section: Unifying Object Versions: Temporal Rolementioning

confidence: 99%

StratOSphere: unification of code, data, location, scope, and mobility

Agrawal

Abbadi

1999

Proceedings of the International Symposium on Distributed Objects and Applications

View full text Add to dashboard Cite

The StratOSphere system provides a framework for distributed objects written in Java, unifying mobile code and distributed programming systems by providing the basic entities: relocatable instances and methods, persistent repositories, and mobile execution state. Each StratOSphere host provides a repository to store object instances and methods in a persistent manner. The repository is partitioned among different hosts, to distribute the storage of objects, and to provide different implementations of an object specification among particular hosts. Client applications visit relevant repositories to acquire specialized behavior from methods stored within the repository. At run-time these entities can be accessed and dispatched, providing a means of invoking an operation in a dynamic fashion, while still ensuring type safety and correctness. In addition to unifying externally-defined methods with compiled objects, and providing location transparency through mobility, StratOSphere further unifies different versions of an object, permitting successive implementations to coexist within the system. We discuss the architecture and implementation of StratOSphere, describing how the goals of unifying different aspects of distributed computing have influenced its design.

show abstract

“…A variety of versioned data stores are available on the market today including Oracle's relational Workspace Manager [13], Microsoft's Repository object store [2] [3], and IBM's Clearcase file store [10] and numerous content management systems. Once standard coordination protocols and resource manager APIs are available, developing the resource managers on top of the versioned data stores is straight-forward.…”

Section: Web Workpace Implementationmentioning

confidence: 99%

Collaboration and undo: the Web workspace paradigm

Swart

Proceedings of the 7th International Conference on Properties and Applications of Dielectric Materials (Cat. No.03CH37417)

View full text Add to dashboard Cite

An informal look at some of the most annoying problems confronting users who attempt to manipulate data stored on the web and a new update paradigm that handles many of these problems. This new approach, called Web Workspaces, allows for collaboration, undo, 'what if' analysis, auditing and a form of long running transaction. The new approach builds on Workspace Versioning techniques long in use in CASE and CAD systems and on transaction coordination techniques, long used to turn disparate applications into cohesive systems. The ideas can be applied to Web Services or to Enterprise frameworks to build more robust and usable applications for manipulating data on the web.

show abstract

Versions and workspaces in Microsoft repository

Cited by 6 publications

References 7 publications

DATABASE VERSION CONTROL - A Software Configuration Management Approach to Database Version Control

DATABASE VERSION CONTROL - A Software Configuration Management Approach to Database Version Control

StratOSphere: unification of code, data, location, scope, and mobility

Collaboration and undo: the Web workspace paradigm

Contact Info

Product

Resources

About