Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
would you use springs AOP (aspects) if you had to track user points throughout your application?
it seems like a potential fit, since points are awarded etc. throughout the application, kind of like security checks.
(just reading on AOP, trying to grasp its potential and usage other than say security or logging).
when you wire up your joinpoints, are they “setup” on the fly or once? I’m just concerned as to how this effects performance, or is it a non-issue really?
Yes, this sounds like a good use of AOP.
As to the specifics of how it works, that depends which AOP framework you’re using. Some do the aspect weaving at compile time (e.g. AspectJ CTW), some do it when the lasses are loaded (e.g. AspectJ LTW), some do it dynamically at runtime (e.g. Spring AOP).
There is an inevitable performance impact, but don’t let that stop you from giving it a go.