search

AscSecTeam / knackered

Scoring Engine API Service
MIT License
0 stars 0 forks source link

pick a web framework for the service #3

Closed brettlangdon closed 10 years ago

brettlangdon commented 10 years ago

My vote here is on flask, http://flask.pocoo.org/.

Mostly because it is easy to use and to figure out for the first time. It is a pretty common framework that people use, but also because of blueprints, http://flask.pocoo.org/docs/blueprints/

With blueprints we can create modular mini apps and then basically add them all together to create the service. e.g. we have a separate config app which is a blueprint which defines the /team/info, /team/add, /team/remove, etc end points, then we can register that blueprint to the main app with the url prefix of /config and we end up with endpoints like /config/team/info, /config/team/add, etc. It ends up allow for nice modular web apps.

My 2 cents, would love to hear other peoples thoughts on the matter though and then we can have a vote on which we want to use?

yzguy commented 10 years ago

I second flask, I really like it. Was just today trying to get back into it. If we are writing most of it in Python, we might as well do Flask

brettlangdon commented 10 years ago

I guess we are going with flask... since @yzguy merged my pull request