Distributed garbage collection using reference counting
Volume II: Parallel Languages on PARLE: Parallel Architectures and Languages Europe
An efficient garbage collection scheme for parallel computer architectures
Volume II: Parallel Languages on PARLE: Parallel Architectures and Languages Europe
Working with Persistent Objects: To Swizzle or Not to Swizzle
IEEE Transactions on Software Engineering
Role and task-based access control in the PerDiS groupware platform
RBAC '98 Proceedings of the third ACM workshop on Role-based access control
Garbage collecting the Internet: a survey of distributed garbage collection
ACM Computing Surveys (CSUR)
Application-independent reconciliation for nomadic applications
EW 9 Proceedings of the 9th workshop on ACM SIGOPS European workshop: beyond the PC: new challenges for the operating system
Modelling a Distributed Cached Store for Garbage Collection: The Algorithm and Its Correctness Proof
ECCOP '98 Proceedings of the 12th European Conference on Object-Oriented Programming
Recent Advances in Distributed Garbage Collection
Advances in Distributed Systems, Advanced Distributed Computing: From Algorithms to Systems
Managing schema evolution in a container-based persistent system
Software—Practice & Experience
Pro-active environment for assisted model composition
CDVE'07 Proceedings of the 4th international conference on Cooperative design, visualization, and engineering
| Hi-index | 0.00 |
PerDiS is a distributed persistent middleware platform, intended to ease the distributed sharing of long-term data. Its users belong to geographically-distant and non-trusting entreprises. It targets CAD applications for the building industry: data sets are large and pointerrich; simultaneous reads and updates are supported; there is no central database; migrating legacy applications is accessible to unskilled programmers. A number of real applications have been either ported or writtensp ecifically for PerDiS.The following design decisions were essential to the scalability and to the useability of PerDiS. Isolation (transactions) decouples users from one another. The system design provides different granularities. The programming abstraction is a fine-grain, persistent, isolated shared memory, with objects, invocations and URLs. The system mechanisms are coarsegrained, loosely-coupled and optimistic. Fine-grain application entities are encapsulated into coarse-grain system entities, respectively clusters, domains, transactions, and projects.