CSC/ECE 517 Fall 2007/wiki1b 5 b4: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
'''Hold for Robin Yehle Wiki Assignment 1b''' | '''Hold for Robin Yehle Wiki Assignment 1b''' | ||
AspectR is a very useful Ruby module, but it is not easy to find documentation on it that is appropriate for students taking this class. Find, or construct, documentation that explains what it does without presuming previous knowledge of AspectJ, that describes many or all methods of the module and how they work. Also find or produce an easy-to-understand example that does not involve logging. | AspectR is a very useful Ruby module, but it is not easy to find documentation on it that is appropriate for students taking this class. Find, or construct, documentation that explains what it does without presuming previous knowledge of AspectJ, that describes many or all methods of the module and how they work. Also find or produce an easy-to-understand example that does not involve logging. | ||
==Example: Profiler Aspect== | |||
One common use of AOP is profiling. Profiling refers to the collection of data about the dynamic behavior of a system. It is done to determine a breakdown of where time and memory are being consumed and make optimizations based on the result. In this example, we create an aspect that will determine the number of (milli)seconds spent in a method. It is kept very simple to clearly illustrate the functionality of AspectR, and would need extensive enhancement to actually be used. A full-featured profiler would need to account for non-serialized and nested method invocations, and would need to aggregate the results, for example. | |||
Revision as of 23:12, 30 September 2007
Hold for Robin Yehle Wiki Assignment 1b AspectR is a very useful Ruby module, but it is not easy to find documentation on it that is appropriate for students taking this class. Find, or construct, documentation that explains what it does without presuming previous knowledge of AspectJ, that describes many or all methods of the module and how they work. Also find or produce an easy-to-understand example that does not involve logging.
Example: Profiler Aspect
One common use of AOP is profiling. Profiling refers to the collection of data about the dynamic behavior of a system. It is done to determine a breakdown of where time and memory are being consumed and make optimizations based on the result. In this example, we create an aspect that will determine the number of (milli)seconds spent in a method. It is kept very simple to clearly illustrate the functionality of AspectR, and would need extensive enhancement to actually be used. A full-featured profiler would need to account for non-serialized and nested method invocations, and would need to aggregate the results, for example.