Malte, Patrick, yes it would be cool to have PHP be able to actually
call the OpenACS registration and security code, even more so to have
efficient bi-directional foreign function calls between the two
languages.
But that isn't what Nima is asking for. From what he's said so far,
sounds like all he needs is to restrict access to a bunch PHP pages to
users who pass certain OpenACS-based authentication checks (must be
logged in, must be a member of the university, etc.) As long as he
can predict the URLs of those PHP pages and code them into a
registered filter, he's set. He doesn't actually need any
communication at all between PHP and Tcl, he just needs
AOLserver to refuse to serve the PHP pages unless you're logged into
OpenACS, and to redirect to the OpenACS login page if you're not.
Should be easy.
