It's not easy to write a standard object model that conceptually scales to infinity. I try it about once a year anyway. Each attempt starts with a small set of rules, but their corollaries invariably reach a point where complex applications can't be written. Check out my graveyard of past attempts to see for yourself.
This year's try started off with more modest goals. That didn't prevent the first two attempts from veering off into WTF?! Land. Luckily the third try's taking much longer to go there.
You might like this one. It almost totally abstracts POE::Kernel and POE::Session behind what's so far a small class library. To be sure, its size is a function of its incompleteness rather than its tidiness, but I think it's one of my best attempts to date.
And you'll be happy about its calling convention, which is hash-based rather than using Perl's standard @_ array for parameters. You may not be happy with the choice of parameter (and other) names, but I'm open to suggestions. Keep in mind: This is prototypical code, so it's all subject to change as better ideas come up.
In reply to Re^2: Why are people not using POE?
by rcaputo
in thread Why are people not using POE?
by johnnywang
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |