Re: [Phpwebsite-developers] Scoping & the Theory Of Relativity [long]

[clayton c. <cc...@ca...>]

Todd,

>Their "relation node" concept should be
> our model of inter-object relationships.  Instead of scoping (as defined
in
> ACS), where a group or user relates to an object, the relation node
connects
> arbitrary object types.
i just had a read, and it does seem interesting. Like moving the ER model to
the application level. This should be not too difficult to accomplish,
though i still have to process how cardinality would fit into our scheme.
What this would mean, and what i propose regardless, is that we keep
metadata for every table in our system which is involved in such a
relationship or defines entities which are exposed to the user. this makes a
lot of things easy, as we can have a generic codebase to handle the
neccessary base functions (permissions management, entity-entity mapping,
etc) as well as generating the user interface.

>We should use the mmbase
> permission model or the ACS model (as modified by Clayton).  This allows a
> more abstracted access control scheme.
i searched the PDF and it didnt mention permissions. do you have a reference
?

> The xml-rpc in ezpublish is great.  I propose we use xml-rpc for all
> inter-module communication like telling the email module to send mail
based
> on a new user login "trigger".  This makes the message passing almost ;)
> effortless and meets our commitment to open standards.
i had proposed before the "alert" model. if this works fine, then great.
perhaps we can compare and see which works best, or if a combination would
meet our needs. Alerts as implemented in TerraCotta are DB backed (except
for high priority ones, which are handled immediately), so we can use them
for delayed processing (like bulk invoice generation, etc)



clayton