Aspects Made Explicit for Safe Transactional Semantics [DSN 2006]

67 %
33 %
Information about Aspects Made Explicit for Safe Transactional Semantics [DSN 2006]

Published on May 2, 2008

Author: khoffman

Source: slideshare.net

Description

Implementing the transactions cross-cutting concern in AspectJ faces many challenges. We propose making join points an explicit part of the base code to overcome these challenges.

Aspects Made Explicit for Safe Transactional Semantics Kevin Hoffman / Patrick Eugster

Properties of Transactions  A tomicity – all or nothing  C onsistency – changes respect specifications  I solation – effects of concurrency masked  D urability – committed results never lost Kevin Hoffman and Patrick Eugster -2-

Implementation Approaches Library approach Language approach - Safety +Safety - Elegance +Elegance +Flexibility - Flexibility +Interoperability - Interoperability Kevin Hoffman and Patrick Eugster -3-

Add a comment

Related presentations

Related pages

Aspects Made Explicit for Safe Transactional Semantics

Aspects Made Explicit for Safe Transactional Semantics Kevin Hoffman Purdue University kjhoffma@cs.purdue.edu Patrick Eugster Purdue University peugster@cs ...
Read more

DSN-2006 Full Program

(DSN-2006) Sheraton Society ... DSN Invitation. Home Page; Program at a glance; Full Program; Registration; ... Aspects Made Explicit for Safe ...
Read more

Kevin Hoffman: Graduate Student at Purdue University ...

Aspects Made Explicit for Safe Transactional ... Kevin Hoffman and Patrick ... "Aspects Made Explicit for Safe Transactional Semantics", DSN 2006, ...
Read more

Supplemental Proceedings of DSN 2006

Supplemental Proceedings 2006 International Conference ... Philadelphia, PA. DSN 2006. Table of ... Aspects Made Explicit for Safe Transactional Semantics ...
Read more

Dsn | LinkedIn

View 11133 Dsn posts, presentations, experts, and more. Get the professional knowledge you need on LinkedIn. LinkedIn Home What is LinkedIn? Join Today
Read more