Procedures as persistent data objects
ACM Transactions on Programming Languages and Systems (TOPLAS)
Fixing the “broken-link” problem: the W3Objects approach
Proceedings of the fifth international World Wide Web conference on Computer networks and ISDN systems
Garbage collection: algorithms for automatic dynamic memory management
Garbage collection: algorithms for automatic dynamic memory management
A type system for dynamic Web documents
Proceedings of the 27th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
A compliant persistent architecture
Software—Practice & Experience - Persistent object systems
The influence of browsers on evaluators or, continuations to program web servers
ICFP '00 Proceedings of the fifth ACM SIGPLAN international conference on Functional programming
XL: an XML programming language for web service specification and composition
Proceedings of the 11th international conference on World Wide Web
ACM Transactions on Internet Technology (TOIT)
Orthogonally persistent object systems
The VLDB Journal — The International Journal on Very Large Data Bases - Persistent object systems
An Overview of the Arjuna Distributed Programming System
IEEE Software
Programming the Web with High-Level Programming Languages
ESOP '01 Proceedings of the 10th European Symposium on Programming Languages and Systems
Uniprocessor Garbage Collection Techniques
IWMM '92 Proceedings of the International Workshop on Memory Management
High-Level Server Side Web Scripting in Curry
PADL '01 Proceedings of the Third International Symposium on Practical Aspects of Declarative Languages
Current Directions in Hyper-Programming
PSI '99 Proceedings of the Third International Andrei Ershov Memorial Conference on Perspectives of System Informatics
Web Engineering: Beyond CS, IS and SE Evolutionary and Non-engineering Perspectives
Web Engineering, Software Engineering and Web Application Development
Web Engineering: A New Discipline for Development of Web-Based Systems
Web Engineering, Software Engineering and Web Application Development
The Memory Behavior of the WWW, or The WWW Considered as a Persistent Store
POS-9 Revised Papers from the 9th International Workshop on Persistent Object Systems
VLDB '99 Proceedings of the 25th International Conference on Very Large Data Bases
An embedded domain-specific language for type-safe server-side web scripting
ACM Transactions on Internet Technology (TOIT)
Response time in man-computer conversational transactions
AFIPS '68 (Fall, part I) Proceedings of the December 9-11, 1968, fall joint computer conference, part I
Hi-index | 0.00 |
As Web application development evolves from initial ad hoc approaches to large scale Web engineering, it is increasingly important to adopt systematic approaches to ensuring safety properties of Web applications. In particular, engineers constructing Web applications should be provided with at least the same guarantees of static safety as in preceding development paradigms; the current absence of such guarantees leads to Web application users being forced to endure failure modes that would never be accepted from conventional applications. We observe that much is known about program safety in the traditional software development domain. Based on this observation, we contend that Web engineering should adopt an evolutionary rather than revolutionary approach to program safety. That is, existing solutions from conventional development should be evolved to match the exigencies of the Web engineering context, rather than engendering solutions that are wholly new. With this evolutionary approach in mind, we introduce a categorisation of the problem area into four major safety properties, each related by analogy to a problem in the conventional development paradigm. Further, we observe that in the Web context, these properties are interrelated, and hence adopt an integrated model for their enforcement. Based on this integrated model, we demonstrate an approach to Web application safety that is both simpler and more powerful than previous, non-integrated, approaches. In contrast to previous systems, our approach as implemented in our WebStore application server achieves the safety goals without recourse to new and unfamiliar programming constructs. Finally, WebStone benchmark results comparing our server to existing mainstream Web application development platforms demonstrate that it provides acceptable performance for a wide range of Web applications.