Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Choose some AOP framework #61

Closed
s-kostyuk opened this issue Feb 12, 2018 · 1 comment
Closed

Choose some AOP framework #61

s-kostyuk opened this issue Feb 12, 2018 · 1 comment
Assignees
Milestone

Comments

@s-kostyuk
Copy link
Owner

Choose some AOP framework to be able to:

  • perform centralized logging of Service calls;
  • open and close DB transactions;
  • check if an access to the requested resource or actions is allowed (permission control)

So, some sort of middleware is needed to perform such tasks prettily

@s-kostyuk s-kostyuk self-assigned this Feb 12, 2018
@s-kostyuk s-kostyuk added this to the v0.3 milestone Feb 12, 2018
@s-kostyuk s-kostyuk mentioned this issue Feb 12, 2018
3 tasks
@s-kostyuk
Copy link
Owner Author

s-kostyuk commented Feb 21, 2018

OK, the following decisions was made:

  • ready-made AOP framework will not be used;
  • I'll not implement a fully-featured AOP framework by my own;
  • Interceptor pattern will be used for implementation of Aspects;
  • dynamic nature of the Python language will be used for implementation of Interceptors;
  • interceptor objects will be created in runtime explicitly on everpl start-up, just after instantiation of the corresponding objects to be wrapped (like Services);
  • Authorization checking will be implemented via Context Managers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant