node_access

Check it out.
http://drupaldojo.blip.tv/file/3966199/

This session will cover how drupal controls access (who can view, create, edit, and delete) nodes/content. It will cover how drupal checks access, what modules can do to expand on that, and what you can do to insure that access is being checked. There will be some code, but mostly as background images.

As we all know, block caching is very useful. However, on complex social/web 2.0 sites with a node_access module (like organic groups) block caching is disabled, because core doesn't allow block caching and a node access module running at the same time. While this is a weird architectural issue, I am wondering about best practices to deal with this on a drupal site with many authenticated users and a node_access module.

Take these questions for this situation:

I have the need for a site where I can define access to individual nodes by user. In this scenario, access by permission or roles is not finite enough. Node_Access has this ability. But when I want to create a view to display the node available to a given user, View's Access setting overrides the permission and roles settings in Node_Access. There is a similar module, Content Access that tries to solve a similar problem.

What is the difference between the table nodeaccess and the table node_access? Do I need both of them?