-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Henri Kaukola wrote: | | First of all, NAP is the helper function of traversing a content tree. | | It was | | built for that, and just does that. That it does not inherently support | | viewer | | groups, is a NAP problem, not one of the elements build on NAP. Again, | | instead | | of building these checks into each and every place, NAP should check | | this even | | when loading NAP data, so that the Sitemap would only see what its | | allowed to see. | | Bergie asked me to remind people about MIDCOM_NAV_VISIBLE, | that is available in NAP. Basically all components should | check for true/false before displaying anything. This check | takes into account the ViewerGroups settings.
This is exactly what I ment.
Reimplementing these checks in each component is senseless. It is not the business of the components to make general checks for access permissions.
Yes, components do set the visible flags, partly does NAP (in case of ViewerGroups), but why should an element that is actually invisible go into the NAP response in the first place?
So many open ends in MidCOM ... :-(
Live long and Prosper! Torben Nehmer
- -- Torben Nehmer, Guenzburg, Bavaria, Germany http://www.nathan-syntronics.de, mailto:[EMAIL PROTECTED] PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB+MvjJPh4Kn6d5FYRApeMAJ4xwGF6DQl5kMCA/75gmDWb9uwYBgCg8RiR 6qPNBERuCCooxUqqlDjfm5E= =cA+R -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
