CSC/ECE 517 Summer 2008/wiki1 5 a5: Difference between revisions
No edit summary |
No edit summary |
||
Line 65: | Line 65: | ||
Java is statically type language. It doesn’t provide any language level ability to monitor events like object creation etc. However, the latest JVM version through '''[http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html JVMTI]''' allow some hooks for monitoring performance but there is no way for the developer to change the behavior of an application through the available hooks. | Java is statically type language. It doesn’t provide any language level ability to monitor events like object creation etc. However, the latest JVM version through '''[http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html JVMTI]''' allow some hooks for monitoring performance but there is no way for the developer to change the behavior of an application through the available hooks. | ||
=== Benefits of Hooks === |
Revision as of 13:39, 5 June 2008
Introduction
Ruby has hooks that allows trapping a certain event (e.g., object creation) and running a particular code sequence whenever the event occurs. There's no comparable facility in Java. But both Ruby and Java have support for aspect-oriented programming (AspectR and AspectJ, respectively). What's the difference between simply providing hooks, and supporting full AOP, and why is it more convenient to program this way in Ruby than Java? Give a few code sequences to justify your conclusions.
Hooks
There is a strong desired from developers to have control on object life cycle. They would like to know when an object is created or destroyed, or some specific method is executed. They would like to monitor what application is doing inside and look for possibility to change application behavior or add new functionality without making big changes in object model.
Hooks Implementation
Most of dynamic languages provide some ways to execute custom code at different steps of object life cycle. Most of them built this functionality as part of language design. They use interceptor design pattern as implementation guideline.
Hooks in Ruby
Ruby is a dynamic and pure object oriented language. It has a very strong support for metaprogramming. It provides system hooks for monitoring events like object creation. The technique use by Ruby to provide this functionality is a simple example of interceptor design pattern. By intercepting calls to system classes developer could modify the system behavior without changing application code.
Example Code:
Following is an example code from Programming Ruby - The Pragmatic Programmer's Guide (First edition is freely available on web) for hooking objects creation event. This code modifies two Ruby system classes (Class and Object). It renames and redefines the Class new method and modifies the Object class to store timestamp.
class Class alias_method :old_new, new def new (*args) result = old_new(*args) result.timestamp = Time.now return result end end class Object def timestamp return @timestamp end def timestamp = (aTime) @timestamp = aTime end end
Now, lets run some tests:
class Test end obj1 = Test.new sleep 2 obj2 = Test.new obj1.timestamp obj2.timestamp
Hooks in Java
Java is statically type language. It doesn’t provide any language level ability to monitor events like object creation etc. However, the latest JVM version through JVMTI allow some hooks for monitoring performance but there is no way for the developer to change the behavior of an application through the available hooks.