Pattern languages of program design 3
A study on exception detection and handling using aspect-oriented programming
Proceedings of the 22nd international conference on Software engineering
Journal of Systems and Software
A recovery mechanism for modular software
ICSE '79 Proceedings of the 4th international conference on Software engineering
Some Misconceptions About Lines of Code
METRICS '97 Proceedings of the 4th International Symposium on Software Metrics
ICCL '98 Proceedings of the 1998 International Conference on Computer Languages
Memory Exclusion: Optimizing the Performance of CheckpointingSystems
Memory Exclusion: Optimizing the Performance of CheckpointingSystems
Extending object-oriented languages with backward error recovery integrated support
Computer Languages, Systems and Structures
AspectScript: expressive aspects for the web
Proceedings of the 9th International Conference on Aspect-Oriented Software Development
Hi-index | 0.00 |
The way developers usually implement recoverability in object oriented applications is by delegating the backward error recovery logic to the ever-present database transactions, discarding the in-memory object graphwhen something goes wrong and reconstructing its previous version from the repository. This is not elegant from the point of view of design, but a cheap and efficient way to recover the system from an error. In some architectures like RIA, the domain logic is managed in the client without that resource, and the error prone and complex recoverability logic must be implemented manually, leading to a tangled and obfuscated code. An automatic recovery mechanism is adapted to that architecture by means of a JavaScript implementation. We developed several benchmarks representing common scenarios to measure the benefits and costs of this approach, evidencing the feasibility of the automatic recovery logic but an unexpected overhead of the chosen implementation of AOP for JavaScript.