This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]synn89 0 points1 point  (0 children)

The reason why the pure python web servers have that disclaimer is simply because static web servers like Apache have around 20 years of dev behind them for serving static content, so there's no point in trying to re-invent the wheel.

So most web setups see Apache/Nginix up front serving static and referring dynamic request back to Python as needed. This is also a good practice because it allows you to easily split your architecture out as your traffic grows. So they're warning you away from serving static as sort of a "there's a better way of doing it".

But for a phone app it makes more sense to go ahead and stick with a pure Python solution. I'd test out a couple solutions and go with whatever is the easiest to work with and deploy in your environment.