misc:alternative_architecture_for_hybrid_applications
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
misc:alternative_architecture_for_hybrid_applications [2016/07/06 13:57] – [PHP] mithat | misc:alternative_architecture_for_hybrid_applications [2016/07/17 03:33] – [PHP] mithat | ||
---|---|---|---|
Line 43: | Line 43: | ||
==== PHP ==== | ==== PHP ==== | ||
+ | * Attractive because it facilitates a lot of web developers get into embedded development (i.e., lots of devs know PHP very well). | ||
* What server? | * What server? | ||
+ | * Is the built-in server good enough for a limited number of connections? | ||
* Is there a native PHP server that is good enough? | * Is there a native PHP server that is good enough? | ||
* [[https:// | * [[https:// | ||
Line 81: | Line 83: | ||
* My [[http:// | * My [[http:// | ||
* My [[http:// | * My [[http:// | ||
+ | |||
+ | ==== Python ==== | ||
+ | * Python is attractive because RPi developers will know it. | ||
+ | * Flask and Flask-RESTful are a good combination. | ||
+ | * Has a development server that might be good enough for a limited number of clients. | ||
+ | * Has the " | ||
+ | * Config files and sqlite are TODO. | ||
===== Client ===== | ===== Client ===== |
misc/alternative_architecture_for_hybrid_applications.txt · Last modified: 2016/07/22 21:42 by mithat