Acl을 사용해야 하는 경우.

간단한 App의 경우 보통 시큐리티의 Url 및 Roll 가지고 보안관련해서 처리를 할 수 있다.

Complex applications often will find the need to define access permissions not simply at a web request or method invocation level. Instead, security decisions need to comprise both who (Authentication), where (MethodInvocation) and what (SomeDomainObject). In other words, authorization decisions also need to consider the actual domain object instance subject of a method invocation.

Imagine you're designing an application for a pet clinic. There will be two main groups of users of your Spring-based application: staff of the pet clinic, as well as the pet clinic's customers. The staff will have access to all of the data, whilst your customers will only be able to see their own customer records. To make it a little more interesting, your customers can allow other users to see their customer records, such as their "puppy preschool" mentor or president of their local "Pony Club". Using Spring Security as the foundation, you have several approaches that can be used:

간단한 예를 들면 내가 작성한 글을 나와 관리자만 볼 수 있고, 다른 사람은 못보게 하자.
이런 내용.

영어공부를 많이 해야 하는데 -_-..
이거 원 맨날 내맘대로 번역이야.