Modular Architectures with Ruby
Summary:
Any reasonably complex end-user application is going to require some sort of customization and enhancement for effective deployment. This article shows one way to create a modular architecture as a way of leaving the door open for advanced users or consultants who want to extend the functionality without modifying the source.
The ability to add new comments in this discussion is temporarily disabled.
Most recent reply: January 18, 2006 3:57 PM by
andresbube
|
|
|
Nice article. This kind of article lets me map concepts between what I know and Ruby. I have a Java background but I'm just starting with Ruby.
I understand the pattern you're trying to implement, but it seems a bit strange that there is no "Interface". Because of that you need to define an empty class returning nill on each method, something like an abstract class.
It is very common to define an extensible architecture or and API based on Interfaces, it happens all the time in Java (i.e. JDBC, XML Parsers, etc...) and other OO languages. How is this supported by Ruby?
|
|