| 
|
Topic: change notification
topics >
computer science >
programming >
change
Topic:
database agents
Topic:
database change management
Topic:
dependency analysis
Topic:
design for change
Topic:
event controlled processing
Topic:
examples of coordination systems
Topic:
management of large software projects
Topic:
managing changes in hypertext
Topic:
optimistic update for concurrency control
Topic:
programming environment
Topic:
renaming
Topic:
software change management
Topic:
software review
Topic:
team programming
Topic:
version control
Topic:
waitfor condition in parallel processing
Subtopic: notification
Quote: all large and widely used systems are subject to an endless stream of changes
Subtopic: what has changed
Quote: coordination deals with synchronous activity while notification deals with asynchronous activity Quote: improve coordination by revealing agents' states through notification; since easier to avoid conflicts than to resolve them [»wexeA4_1992]
Subtopic: important events
Quote: users must be able to find all changes made by others to a Hypertext [»akscRM5_1984] Quote: if translate between type hierarchies for semi-structured messages, need to notify other groups of changes [»leeJ3_1988] Quote: medical information searchers need an agenda-keeper to keep track of new ideas, readings, and tasks [»frisME7_1988] Quote: ZOG 'find' command creates lists of all frames changed since a given date [»akscRM5_1984]
Subtopic: obsolete items
Quote: DSEE can automatically send alarms for changes to a tasklist [»leblDB5_1984] Quote: collaborating users should be notified when important events occur to nodes or links [»halaFG7_1988] Quote: when DSEE's history manager receives a user's modification comments it sends copies to the task's transcript [»leblDB5_1984] Quote: DES for software maintenance; automatic change notification, system simulation [»grahRM2_1973, OK]
Subtopic: broadcast notification
Quote: an 'obsolete' routine in Eiffel generates a compile-time descriptive message and does not appear in the class's short form [»meyeB9_1990]
Subtopic: dependencies
Quote: with broadcast communication, anyone interested in a change can respond to it [»balzRM_1986] Quote: notification and queries need broadcast to convey results and locate services; e.g., reduces demand on centralized directories [»cherDR4_1984]
Subtopic: lock breaking
Quote: in source control, users should define dependencies between elements for warnings prior to changes and notification after changes [»leblDB5_1984]
Subtopic: answer notification
Quote: in RCS, lock breaking automatically sends an e-mail message to the lock's owner; only used in real emergencies or if owner resigns [»tichWF7_1985]
Subtopic: propagation
Quote: if users don't find a question in Answer Garden; they enter a new question that will be answered by an expert via automatic notification [»ackeMS_1990]
Subtopic: caching
Quote: changes to a structure propagate to all of its references, both direct and indirect
Quote: use callbacks for change notification of cached files; must reestablish after notification and periodically confirm
[»satyM4_1990]
Topic: change (28 items)
Topic: database agents (10 items)
Topic: database change management (12 items)
Topic: dependency analysis (34 items)
Topic: design for change (76 items)
Topic: event controlled processing (46 items)
Topic: examples of coordination systems (23 items)
Topic: management of large software projects (63 items)
Topic: managing changes in hypertext (21 items)
Topic: optimistic update for concurrency control (35 items)
Topic: programming environment (46 items)
Topic: renaming (10 items)
Topic: software change management (48 items)
Topic: software review (80 items)
Topic: team programming (7 items)
Topic: version control (34 items)
Topic: waitfor condition in parallel processing
(20 items)