EDBT 2026 Demo / reviewers in the wild / expert
Vicraj T. Thomas
dblp:44/1805
· DBLP profile ↗
3ranked-venue papers
0as first author
0since 2021 · last 1995
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1Security and privacy · 1Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Programming languages and type systems · 50% Operating systems · 50% |
Topics — the 5 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Distributed systems
fault tolerance |
0.0 | 1 | 1995 | Programming Language Support for Writing Fault-Tolerant Distributed Software · IEEE Trans. Computers 1995 |
Distributed systems
programming language support |
0.0 | 1 | 1995 | Programming Language Support for Writing Fault-Tolerant Distributed Software · IEEE Trans. Computers 1995 |
Programming languages and type systems
distributed programming languages |
0.0 | 1 | 1995 | Programming Language Support for Writing Fault-Tolerant Distributed Software · IEEE Trans. Computers 1995 |
Operating systems › fault tolerance
fault tolerance mechanisms |
0.0 | 1 | 1995 | Programming Language Support for Writing Fault-Tolerant Distributed Software · IEEE Trans. Computers 1995 |
Distributed systems › replication › replication and fault tolerance
replication and recovery |
0.0 | 1 | 1995 | Programming Language Support for Writing Fault-Tolerant Distributed Software · IEEE Trans. Computers 1995 |
Methods — techniques the papers use, named apart from their topics
runtime implementation · 0.0language extension · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1995 | Programming Language Support for Writing Fault-Tolerant Distributed SoftwareabstractGood programming language support can simplify the task of writing fault-tolerant distributed software. Here, an approach to providing such support is described in which a general high-level distributed programming language is augmented with mechanisms for fault tolerance. Unlike approaches based on sequential languages or specialized languages oriented towards a given fault-tolerance technique, this approach gives the programmer a high level of abstraction, while still maintaining flexibility and execution efficiency. The paper first describes a programming model that captures the important characteristics that should be supported by a programming language of this type. It then presents a realization of this approach in the form of FT-SR, a programming language that augments the SR distributed programming language with features for replication, recovery, and failure notification. In addition to outlining these extensions, an example program consisting of a data manager and its associated stable storage is given. Finally, an implementation of the language that uses the x-kernel and runs standalone on a network of Sun workstations is discussed. The overall structure and several of the algorithms used in the runtime are interesting in their own right.> Richard D. Schlichting, Vicraj T. Thomas |
IEEE Trans. Computers | 2 |
| 1992 | A Mult-Paradigm Programming Language for Constructing Fault-Tolerant, Distributed SystemsabstractThe design of FT-SR, a programming language based on SR and oriented toward constructing fault-tolerant distributed systems, is presented. The language, which is based on the existing SR language, is unique in that it has been designed to support equally well any of the programming paradigms that have been developed for this type of system, including the object/action model, the restartable action paradigm, and the state machine approach. To do this, the language is designed to support the implementation of systems modeled as collections of fail-stop atomic objects. Such objects execute operations as atomic actions except when a failure or series of failures cause underlying implementation assumptions to be violated; in this case, notification is provided. An example program consisting of a data manager and its associated stable storage is given.> Richard D. Schlichting, Vicraj T. Thomas |
SRDS | 2 |
| 1989 | Tools for Implementing Network Protocols
Norman C. Hutchinson, Shivakant Mishra, Larry L. Peterson, Vicraj T. Thomas |
Softw. Pract. Exp. | 4 |