OK, sounds good. I added a subclass-based version to that code, but it
basically does what you said. Thanks for letting me talk through the
process.

(If anyone is curious about the final implementation, you can follow
it as part of Ringsail within a month or so.
https://github.com/measuredvoice/ringsail )

Thanks,
~chris

On Thu, Nov 17, 2011 at 3:10 PM, Robert Kaufman <[email protected]> wrote:
> Hi Chris,
>  You are on a very reasonable track.  You could simplify it by making Service 
> a module which defines an interface and automatically registers includers 
> using the included call backs.  However, that seems like a stylistic 
> difference more than anything else, and I'd be hard pressed to argue against 
> the specificness that you are using here.  I would lean away from making the 
> whole thing more complex than it needs to be with regards to some sort of 
> plugin architecture.
>
> Best,
> Rob
>

-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to