-----Original Message----- From: Michel Pelletier [mailto:michel@digicool.com] Sent: vrijdag 1 oktober 1999 16:00 To: 'alwyns@prism.co.za'; zope@zope.org Subject: RE: [Zope] Structure of website How?

...

-----Original Message----- From: Alwyn Schoeman [mailto:alwyns@prism.co.za] Sent: Friday, October 01, 1999 8:29 AM To: zope@zope.org Subject: [Zope] Structure of website How?

...

there must be areas for each client. The client must log in and then be transported to his site which lists only the services that the client has subscribed to, client specific news, etc. All client sites must be similar and only differ on authentication and services subscribed. Each site must be private from other clients and Read the Content Managers Guide. It describes this very scenario. As an example, have a folder called general, in which is a folder for each client:

general/ client1/ client2/

...

but, how do you implement the following: in /clients an http authentication should be issued. Depending on the user that logged in, zope should scan the subdir/objects to check which ones he can access, and only display those to the client. example: client A goes to /clients zope asks his login/pw zope checks the subdirs: /clients/newsforclientA /clients/newsforclientB /clients/newsforclientAandB and only displays 2 links (to /clients/newsforclientAandB and /clients/newsforclientA Any ideas? Maarten.