Minor notes: I thought "apply" was now "activate." Major design: Create/Delete broadcast. Isn't this a refinement of Transition? Node create should (?) trigger an automatic deployment of the implicit barclamps. Node Delete would to all barclamps that have been deployed.
Since Jig is the class that handles actual node interaction, shouldn't it be the home of all (most?) of the transition code? Springtime! -judd On Fri, Mar 8, 2013 at 1:47 PM, <[email protected]> wrote: > As we’re flushing out Jigs, I’d like to throw out this pattern as an idea > (Rdoc rules, but this is not yet committed):**** > > ** ** > > =begin**** > > The Jig (base class) provides abstract interface for jig > implementations. The general pattern**** > > is that the base class provides class methods, that either:**** > > - locate the appropriate Jig instance and call the instance method on > them**** > > - call the respective instance method on all jig's**** > > ** ** > > The exact pattern depends on the operation - some operations are > 'broadcast' in nature, **** > > while some should only target a particular jig instance.**** > > =end**** > > ** ** > > Some examples:**** > > **· **Applying a proposal – should only be sent to the Jig that > should handle that proposal.**** > > **· **Creating(e.g. when a node is discovered)/Deleting(e.g. user > deletes) a node – should probably be a broadcast to all Jig’s.**** > > ** ** > > ** ** > > Thoughts?**** > > _______________________________________________ > Crowbar mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/crowbar > For more information: http://crowbar.github.com/ > -- Judd Maltin T: 917-882-1270 F: 501-694-7809 what could possibly go wrong?
_______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
