Group:
distributed database
Topic:
archives
Topic:
broadcasting information
Topic:
concurrency control by sequencers
Topic:
event time
Topic:
immutable files and data
Topic:
implementing distributed systems and applications
Topic:
reliable communication
Topic:
replicated data
Topic:
system builds
Topic:
temporal database
Topic:
temporal relationships
Topic:
time
Topic:
version control
Topic:
version identification
Topic:
updating information in a distributed system
| |
Summary
A timestamp is temporal data stored with an object. Timestamps may indicate the creation time, access time, or modify time. A sequence of timestamps may mark different versions. They are particularly important in communication and security protocols.
Timestamps may be any monotonic number sequence, though they usually corresponding to physical time. An application may require unique timestamps.
Temporal data may require different algorithms. The order of the data must be retained, complicating analysis. (cbb 2/07)
Subtopic: version by timestamp 
| Quote: current information by most recent timestamp; past information by previous timestamp
| | Quote: represent modified object by original surrogate, new timestamp, modified data [»copeG3_1980]
| | Quote: time domain addressing for transactions in immutable systems; two timestamps per version for created and last read [»walpJ6_1988]
|
Subtopic: unique timestamp
| Quote: if need to guarantee uniqueness of timestamps in a network, require one tick between each local timestamp and qualify with siteid [»bernPA5_1978]
| | Quote: implement time by a timestamp on each message; receiver advances its process time to be later than the timestamp [»lampL7_1978]
|
Subtopic: query of timestamped data
| Quote: with timestamped data, queries can be concurrent with updates by using previous copy [»copeG3_1980]
| | Quote: if an analysis uses an item that becomes modified, the former value has a timestamp to limit its validity [»shavMJ2_1980]
| | Quote: with time-split b-trees, read-only transactions only need a timestamp for concurrency control; ignores all later records [»lomeD6_1989]
|
Subtopic: timestamp vs. event clock
| Quote: efficient algorithm to convert timestamps into event clocks; reduces state space for model checker of distributed protocols [»dereF3_2001]
|
Subtopic: timeout
| Quote: distributed appications generally require timeouts for asynchronous communcation and failures; e.g., TCP [»bishS1_2006]
|
Subtopic: time server
| Quote: V uses time servers to serialize access to resources; better than monitors since independent of client [»cherDR4_1984]
|
Subtopic: security protocol
| Quote: allow skewed clocks in the Kerberos Authentication System by acquiring time-service tickets at bootstrap [»daviD6_1995]
|
Subtopic: authentication
| Quote: use timestamps for tamper-unpredictable documents, i.e., when the motivation to illegally modify a document occurs long after the document's creation [»harbS2_1991]
| | Quote: timestamp documents with a one-way hash; either use a server which links a document to other documents, or use a random subset of clients [»harbS2_1991]
| | Quote: timestamps are an effective mechanism to authenticate photographs, videos, and audio recordings
|
Subtopic: ID reuse after T seconds
| Quote: Thoth depended on T-stability (ids not reused in <T seconds); difficult to implement in a distributed environment [»cherDR3_1988]
|
Subtopic: security and timestamps
| Quote: can solve problem of message replays by adding time-stamps to encrypted messages; needs secure private keys and delay bounds [»dennDE8_1981]
|
Subtopic: distributed update
| Quote: update name directory copies by point-to-point messages backed by a global sweep for all updates before some time-stamp [»lampBW8_1985]
|
Subtopic: cached data
| Quote: use version stamps for cached data shared by multiple threads; raise an exception if the version stamp does not match [»birrAD_1991]
|
Related Topics
Group: distributed database (6 topics, 194 quotes)
Topic: archives (19 items)
Topic: broadcasting information (18 items)
Topic: concurrency control by sequencers (27 items)
Topic: event time (45 items)
Topic: immutable files and data (59 items)
Topic: implementing distributed systems and applications (41 items)
Topic: reliable communication (29 items)
Topic: replicated data (51 items)
Topic: system builds (43 items)
Topic: temporal database (25 items)
Topic: temporal relationships (40 items)
Topic: time (49 items)
Topic: version control (34 items)
Topic: version identification (12 items)
Topic: updating information in a distributed system
(50 items)
|
