Friday 15 August 2008 11:57:46 pm
Here's an additional example of what I am after: 1) There is a folder in the content node tree called <b>User groups</b>. This cannot be altered by users, but users can publish beneath it. + Site [Root]
++ User groups [folder]
2) Any user can go to that <b>User groups</b> folder and create a node based on <b>User group class</b>. That user will be an owner of that node and the owner/initiator of newly created group at the same time. Let's say a user creates a restricted user group called <b>Pink socks fans</b>: + Site [Root]
++ User groups [Folder]
+++ Pink socks fans [Restricted user group]
3) Restricted user group class means that it can only be accessed for users that belong to that group. In other words, users will not have permission to access that subtree, unless allowed otherwise. Users that are allowed in, should be able to create further structure, for example in a forum-like way: + Site [Root]
++ User groups [Folder]
+++ Pink socks fans [Restricted user group]
++++ I've lost my pink left sock [Restricted forum subject]
+++++ Wear just one [Restricted forum reply]
+++++ Buy a new one [Restricted forum reply]
++++ Shades of pink [Restricted forum subject]
...
4) Users have to follow a special procedure in order to be let into this group. For example, they have to declare that they want to belong there. Once they do so, a proper access control system modification should be performed to grant that user access to this particular <b>Pink socks fans</b> subtree. And one more thing: users can be members of any number of restricted groups!
And now the questions: Do you think that eZ Publish with its RBAC would be capable of handling that and if so, what size of community are we talking about? Would it be possible to have a community of 1000 restricted groups with 10000 registered users who are member of 20 restricted groups on average? What about larger communities? Thanks is advance!
--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu
|