Considerations on fine-grained permission control

Permission control can be said to be the prerequisite base module for each project, not to discuss RBAC and ACLs, just your own ideas.  

The privilege control in my eyes:

Function: Used to control access to functions or resources, that's all.

Whether it's a SPRINGMVC interceptor or a struts interceptor, it's easy to intercept the address bar operation.  

The problem is how to control permissions at the page level, such as buttons, a resource element, and so on.

Questions about naming conventions:

For example, add features:

@RequestMapping (value= "/role/add.jhtml", Requestmethod=get)

@RequestMapping (value= "/role/add.jhtml", Requestmethod=post)

The request path for both can be the same.

What does this mean? This means that as long as the naming rules are defined, action-level requests can be well-intercepted.

Questions about Page control:

Whether you are a JSP or a freemarker, can you make a custom tag to determine if you have access, and whether it is displayed?

Considerations on fine-grained permission control