Persistent Hyper-Programs

Kirby, Graham N. C.; Connor, Richard; Cutts, Quintin; Morrison, Ronald; Dearle, Alan; Farkas, Alex

doi:10.1007/978-1-4471-3209-7_6

Cited by 28 publications

(21 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The reverse mapping is less so, but given that this can be guided by the embedded type representation it presents no real technical problems. Types such as closures and abstract types present more of a challenge; however previous research on hyper-programming [KCC+92] can be used to solve many of the problems very neatly, by providing a model of closure that bears a textual representation. The issues of protection in abstract data types should also be noted, although it seems unlikely that there is a perfect solution.…”

Section: Representing Persistent Valuesmentioning

confidence: 99%

On the Unification of Persistent Programming and the World-Wide Web

Connor

Sibson

Manghi

1999

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. In its infancy, the World-Wide Web consisted of a web of largely static hypertext documents. As time progresses it is evolving into a domain which supports almost arbitrary networked computations. Central to its successful operation is the agreement of the HTML and http standards, which provide inter-node communication via the medium of streamed files. Our hypothesis is that, as application sophistication increases, this file-based interface will present the same limitations to programmers as the use of traditional file and database system interfaces within programming languages. Persistent programming systems were designed to overcome these problems in traditional domains; our investigation is to reapply the resulting research to the new domain of the Web. The result of this should be the ability to pass typed data layered on top of the existing standards, in a manner that is fully integrated with them. A typed object protocol integrated with existing standards would allow the Web to be used to host a global persistent address space, thus making it a potential data repository for a generation of database programming languages.

show abstract

Section: Representing Persistent Valuesmentioning

confidence: 99%

On the Unification of Persistent Programming and the World-Wide Web

Connor

Sibson

Manghi

1999

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…The browser is also used to select persistent objects for linking into hyper-programs under construction. The benefits of hyper-programming are discussed in Kirby, 1992;Kirby, Connor et al, 1992), and include:…”

Section: Hyper-programmingmentioning

confidence: 99%

Exploiting Persistent Linkage in Software Engineering Environments

Morrison

Connor

Cutts

et al. 1995

The Computer Journal

Self Cite

View full text Add to dashboard Cite

Abstract. Persistent programming systems are designed to provide technology for the construction and maintenance of large, long-lived object-based application systems. Many successful prototypes have been constructed and a large body of application building experience is emerging. Three common attributes of persistent systems are persistent linkage, strong typing and the referential integrity of data. Persistent linkage allows persistent objects to be included in the binding process. Strong typing guarantees that objects are only manipulated in a manner consistent with their type system descriptions. Referential integrity ensures that once a link (reference) to an object is established, its identity is unique and it persists over time. As a consequence no object can be deleted while another refers to it. Here we examine some of the advantages of providing software engineering environments within a persistent object system with strong typing and referential integrity. It is shown how the integration of system specifications, programs, configuration management tools and documentation all within a single persistent environment leads to powerful new techniques. This new power is achieved by sharing structured persistent data across the hitherto enclosing boundaries of system components.

show abstract

“…If the value is a procedure, this source code is similar to the hyper-program model of source code described in [7]. If the value encapsulated in an Octopus is not a procedure, then getSource returns a representation of the value which is suitable for use in hyper-programs.…”

Section: Octopusmentioning

confidence: 99%

“…Persistent systems support incremental construction [4] and component reuse [9] by allowing components to be created, stored in the persistent object store and bindings between them established. Bindings may be established at different times: during program construction, at program compile time and when the program is executing [7].…”

Section: Introductionmentioning

confidence: 99%

Changing Persistent Applications

Farkas

Dearle

1995

Persistent Object Systems

View full text Add to dashboard Cite

During the lifetime of an application, the objects and bindings in a persistent store may require modification in order to fix bugs or incorporate changes. Two mechanisms, Octopus and Nodules, supporting the evolution of persistent applications are presented. The first, Octopus permits code and data values to be evolved, even if they are encapsulated. Type evolution is addressed by the separation of type information from the executable code. In many cases type evolution is possible, without the expense of total or partial system recompilation. Nodules are a complementary mechanism to Octopus in that they allow generic templates to be defined independently of any referencing environment. Nodules may be specialised in order to yield instances by binding them to values and types. When combined into a single system, Nodules and Octopus enable a rich collection of information about the structure and state of applications to be maintained and made available to programmers not only during the construction phase, but during the entire lifetime of applications.

show abstract

Persistent Hyper-Programs

Cited by 28 publications

References 12 publications

On the Unification of Persistent Programming and the World-Wide Web

On the Unification of Persistent Programming and the World-Wide Web

Exploiting Persistent Linkage in Software Engineering Environments

Changing Persistent Applications

Contact Info

Product

Resources

About