Well I do know what the definitions are for the two different logic, and each applies to a different software layer(domain/business and application layer). Nonetheless, real life is not as simple as in theory, its sometimes quite difficult to figure out what methods/behaviors should belong to which layer, at least the difference is not as evident as between business logic and presentation logic, which you can easily identify.

Considering a User Authentification system? Lets say I have a domain model called User for the domain/business layer(it may come with a mapper or DAO, but do not worry about this for now), and a controller object called UserController or RegistrationController/LoginController. What behaviors are domain-specific, and what are application-specific? Anyone mind elaborating with this example? Id appreciate this very much, as it will help me better identify what are domain responsibilities and what are application logic for more complex system.