Re: Simple HTTP framework
Posted: Fri Dec 30, 2016 2:56 pm
@Roberthh that makes a lot of sense. I will start an investigation of porting the existing codebase to use asyncio, likely on a branch off master. In the meantime, I will add a limitation to the current README, to let people know. If anyone is willing to collaborate, please let me know.
Does anyone know the roadmap for asyncio and uselect? Will that code get rolled into a micro python image in the future?
Coincidentally, I started an investigation of using backbone.js and hit the same issues @Adam5Wu reported. I was able to work around some of the issues by loading libraries from their respective web sites and minimizing the number of scripts, but that's obviously not a long-term solution (e.g., for bootstrapping off 192.168.4.1).
Thanks for the heads up. Very helpful!
Does anyone know the roadmap for asyncio and uselect? Will that code get rolled into a micro python image in the future?
Coincidentally, I started an investigation of using backbone.js and hit the same issues @Adam5Wu reported. I was able to work around some of the issues by loading libraries from their respective web sites and minimizing the number of scripts, but that's obviously not a long-term solution (e.g., for bootstrapping off 192.168.4.1).
Thanks for the heads up. Very helpful!