Re: [Phpwebsite-developers] phpWebSite Road Map

[Todd O. <to...@da...>]

See http://www.datadx.com/phpwebsite/ for the eZsession class file and sql
files.  Brian's roadmap has us using native sessions, so consider the above
an educational experience.  Database sessions are a must IF we consider
webserver clusters where server_A will handle client request 1, but server_B
will handle the link to request 2.  I don't forsee a NEED for database
sessions at this precise moment, but I would like to abstract the session
management so they could be added in the future without a rewrite.  On this
same topic, the authentication management should also be similarly
abstracted to allow LDAP at some point in the future too.

The mmbase permissions aren't that easy to explain because they're not in
one place like most of the other projects I listed.  I vote for the ACS
style permissions as translated by Clayton.

I agree with Alain that the object functionality Brian mentioned was the way
I expected.  Does anyone have a link to a PHP discussion of the proposed
change?

I haven't seen any discussion about inter-module communication in the
Roadmap or otherwise.  Did anyone like my xml-rpc proposal?  I think the
"alert" model (Clayton's term) or trigger model (sql term) should be handled
by xml-rpc.  The receiving module would then handle it's own activities,
such as queing email for nightly transfer.  The sending module would get
confirmation that the receiver model got the message and would proceed
accordingly.  This keeps the responsibility of sending emails (let's say) in
the email module.

--Todd