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 revisionLast revisionBoth sides next revision | ||
misc:alternative_architecture_for_hybrid_applications [2016/07/06 13:30] – [Notes/question] mithat | misc:alternative_architecture_for_hybrid_applications [2016/07/17 03:34] – [Notes/questions/issues] mithat | ||
---|---|---|---|
Line 35: | Line 35: | ||
==== Notes/ | ==== Notes/ | ||
* Persistence: | * Persistence: | ||
- | * Security model: | + | * Security model alternatives: |
* Accept connections only from localhost? CORS? | * Accept connections only from localhost? CORS? | ||
* Password (in request) or API key (basic auth) property in app? | * Password (in request) or API key (basic auth) property in app? | ||
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 51: | Line 53: | ||
* Can " | * Can " | ||
- | The above are not issues for embedded application as the machine' | + | The above are not issues for embedded application as the machine' |
* Frameworks | * Frameworks | ||
* Silex | * Silex | ||
+ | * Good community support. | ||
+ | * Good Composer and module support. | ||
+ | * Documentation is a bit obtuse. | ||
+ | * Out of the box twig support. Redbean support is available. | ||
+ | * Has a good ReST code structure but you wouldn' | ||
* Slim | * Slim | ||
+ | * Slim 3 has removed some functionality that might be good to have. | ||
* Fat Free Framework | * Fat Free Framework | ||
+ | * Compact, more than what's needed. | ||
+ | * Excellent ReST code structure. | ||
+ | * Twig and Redbean support are available. | ||
+ | * Not sure Composer is well supported. | ||
+ | * Check cookies/ | ||
* Persistence | * Persistence | ||
* Redbean | * Redbean | ||
Line 62: | Line 75: | ||
* [[http:// | * [[http:// | ||
- | ===== Client ===== | + | ==== Node.js |
- | | + | |
- | | + | * There is also a " |
- | - If served, by a separate server or by the same server that's handling the API? | + | * Frameworks |
+ | | ||
+ | * Persistence | ||
+ | * My [[http://nodejs-configfile.saved.io/ | ||
+ | * 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 ===== | ||
+ | * To be served or simply loaded from file? | ||
+ | * I suspect the former is better because of security/ | ||
+ | * If served, by a separate server or by the same server that's handling the API? | ||
misc/alternative_architecture_for_hybrid_applications.txt · Last modified: 2016/07/22 21:42 by mithat