I've looked this over and tried to get my head around it. I think that the $factory->class_constructor->method($foo) syntax is better, as you indicated in cb, with parens on the constructor to tell perl and everybody that it is a function: $factory->class_constructor()->method($foo). With that, it doesn't look so odd to me.
I'm not familiar with Class::Factory, so at first I spent some time wondering why the driver config files weren't simply set up as modules subclassing the more general categories of interface and protocol layer. That is what POE looks like, as an example of a system with some similarities to your architecture.
Your design grew on me as I studied it, and I'm persuaded to give Class::Factory a closer look.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||