Re: separating which sub- forums can be viewed by "anyone" & "members""

Posted by Hugo <Nabble> on Sep 14, 2011; 5:41am
URL: https://support.nabble.com/separating-which-sub-forums-can-be-viewed-by-anyone-members-tp6752233p6791374.html

I have a few alternative solutions that I want to discuss with you guys. The possible solutions I see are:

A) We could keep the app pages uncached. In other words, each visit to an app page would force the system to read the data from the database and build the HTML from scratch. So the system would build the page based on what the user can view. This would make the site a bit slower, but this shouldn't be an issue if the app isn't so big (e.g., more than 5,000 topics) or heavily visited.

B) Another option is to load the private information with javascript/Ajax. This makes more sense for the MIXED view, where each section is independent of the other. Thus the system would load private subapps with javascript if the user has privileges to view that subapp. For the TOPICS view, the whole table and pagination would have to be retrieved with AJAX and this isn't a good idea. Option A above (no cache) would be better for the TOPICS view.

C) Another option is to continue showing the public information by default on the main cached page, but show a special link to users that can view private/hidden information. The link would go to a page that is not cached and would list everything the user can view.

There is a fourth option that is the best in term of implementation, but this is too much work and we just don't have time for it now. So I would like to hear from you guys what you think about these three options above and we will work on the solution.