> From: Phil Cowans [mailto:[EMAIL PROTECTED]]
>
> I have a specific project which I believe would be well suited to
Cocoon,
> however, the project needs to be served from a machine which provides
web
> hosting for a large number of people. It is conceivable that one
Cocoon is
> installed, other users will want to use it too. Hence I would like to
know
> whether there are any security issues involved with using Cocoon in
this
> way. Particularly, is it possible for multiple users to use the same
> Cocoon installation without having to give them access to each other's
> files,
This is already possible...
> databases etc.
... and this is not yet.
Take a look at <map:mount/>, one of possible use cases is to have one
sub sitemap for every user. It could look like:
<map:match pattern="~*/**">
<map:mount uri-prefix="~{1}" src="/home/{1}/cocoon_pub/"
check-reload="yes"/>
</map:match>
Then every user who have ~/cocoon_pub directory and sitemap.xmap file
under it could have own Cocoon powered site. Every user will inherit
components declared in the parent sitemap, and will have no access to
other user's components/configuration.
Vadim
> Yours,
>
> Phil Cowans
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
