Sorry if I wasn't clear -- I wasn't suggesting that what you've proposed would be made better using the module. Just that if you ever decided to expand it (which often happens IME) it might be useful to look into further decoupling the transactionable (is that a word?) resources from the action doing the commit/rollback.

I don't think the Observer/Observable pattern is too advanced for common use. In fact I think it's one of the simplest (and quickest) ways you can achieve decoupling among disparate processes. Maybe the documentation for Class::Observable is a little too long, but that often happens with simple, flexible little tools that can be used in lots of different ways.

Good luck!

Chris
M-x auto-bs-mode

In reply to Observer pattern and transactions by lachoy
in thread RFC: Transactions.pm by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.