There are several POE::Relationship sub classes mentioned in the TODO file.
I'd like to note that these are patterns which should be layered on a
real link. these relationships (relations would be better) are called
associations between objects (at least in UML and what I've seen so far).
the ends of such associations have a given multiplicity and role(name)s.
these roles identify interfaces on these ends. so interface definitions
for sessions or objects (lets call them objects since they have the same
properties...) should be used as well.
but this is the object layer, actually. I wouldn't mind if it would be used
widely (when one exists), but the last decision I heard from Rocco was that
it shouldn't be included but strictly layered on top. However I do think
that it would make sense for POE basics as well.
I do want to include associations for POE::Script, which will exist soon.
(the plans for it are done, I just need some more time, implementation won't
be so hard). A well designed object layer would be better, but maybe we can
use the script thing as a testcase and to make writing POE scripts more
easily. Roughly it is a stack based method system that deals with parallelism
in the POE way.
Torvald
