concurrent programming vs. concurrency control: shared events or shared data  two views of concurrency in an object system exist. those pursuing concurrent programming believe that activities in the real world are inherently concurrent and therefore objects are themselves active. objects engage in shared events by sending and receiving messages. communicating sequential processes [hoar85a] and actors [agha86a] embrace this view. on the other hand, those pursuing models of concurrency control believe that objects are data and that concurrent access to data needs to be controlled by the system according to some correctness notion. database transactions, atomic objects [weih84a, schw84a] and nested objects [mart88a] embrace this view.  concurrent programming, in our view, places a significant burden on programming. correct concurrent behavior is specified as combinations of interactions within a potentially large set of concurrent objects. a programmer must verify that the implementations of all the objects never produce undesirable interactions. correctness of concurrent behavior is left to the programmer.  we are pursuing models embracing concurrency control primarily because a programmer is not required to consider concurrency. the operations on an object can be specified in terms of preconditions and postconditions and traditional program verification techniques can be used to verify an operation's implementation. a programmer only considers the serial behavior of an object in isolation; he need not concern himself with how other concurrent activities might affect the object. correctness of interleavings is left to the system.  serializability is the usual correctness notion for concurrency control algorithms. in transaction terminology, each competing transaction executes a sequence of basic actions. any interleaving of the actions is correct if it is equivalent to some serial execution of the transaction. serializability allows a transaction to be programmed in isolation, that is without considering possible interleavings with other transactions. the system may indeed interleave the actions of several transactions but it is up to the system to make the interleaving appear serial.  concurrent programming is apparently more general. a programmer can implement anything, including undesirable interactions like deadlock. the price for this generality is that the programmer must reason about global orderings of events and thus correctness is difficult to show.  the traditional transaction model is not general enough for programming shared object systems. for example, several researchers, [bern87a, garc87a, pu88a], have recognized that transactions are too restrictive for long-lived activities. the problem is that the transaction model is too conservative. only reading and writing a data item at a single layer of abstraction is modeled. once a read-write, write-read or write-write dependency is established between two transactions, it remains for the life of the transaction and limits further interleavings.  our approach is to discover and explore less restrictive correctness notions that still allow programmers to implement operations on objects in isolation. in [mart88a] we present two such correctness notions: externally serializable computations and semantically verifiable nonserializable computations. both correctness notions assume the nested object model. in [mart87a] we give a nested object solution to the dining philosophers' problem [dijk71a]. nested objects incorporate both the semantics of an object and the data abstraction hierarchy of an object.  nested objects form a nested object system. a nested object system is hierarchical; objects exist at different levels of the system. the execution of an operation on an object at level i results in the execution of operations on objects at level i-1. however, only top level objects are viewed externally.  a computation at level i is a description of the state change made to level i objects and the return values produced by executing a partially ordered set of operations on level i objects. the computations at each level together form an n-level system computation.  externally serializable computations are n-level system computations in which the top level objects are left in states that could be produced by serial computations. however, lower level objects may be left in states that no serial computation could produce. because both data abstraction hierarchies and operations semantics are considered in the nested object model, dependencies established between concurrent computations can be systematically ignored. long-lived computations can execute efficiently if dependencies can later be ignored.  nested objects are more general than other models of concurrency control. transactions are two-level nested objects that read and write basic data items. atomic objects are two-level nested objects that perform abstract operations.  the 1988 object based concurrent programming workshop did not directly address the differences between concurrent programming and concurrency control. perhaps future workshops can contrast the generality, the applicability, the programmability, the security and the performance implications of models from both concurrent programming and concurrency control.  bruce martin