Confirmed users
1,927
edits
Auto-tools/Projects/WebUXPlatform: Difference between revisions
→Server Architecture
(→Notes) |
|||
| Line 34: | Line 34: | ||
For most apps, a growing consensus is that [http://webpy.org web.py] provides most required functionality for relatively simple web tools. More complex applications might benefit from a heavier framework like [http://www.djangoproject.com Django], which will not be covered here (yet). | For most apps, a growing consensus is that [http://webpy.org web.py] provides most required functionality for relatively simple web tools. More complex applications might benefit from a heavier framework like [http://www.djangoproject.com Django], which will not be covered here (yet). | ||
The standard described here will be client-side apps, that is, applications that have static HTML, CSS, and JS which use server-side REST APIs to update content. See | The standard described here will be client-side apps, that is, applications that have static HTML, CSS, and JS which use server-side REST APIs to update content. See http://metamarketsgroup.com/blog/node-js-and-the-javascript-age/ for a short summary. | ||
The proposed layout is that the index file and other basic content resides at the root, with REST APIs being in a api/ directory. For example, the app 'toolfoo' might be found at http://server/toolfoo/ and its APIs at http://server/toolfoo/api/. Keeping a consistent approach will allow other applications to easily find and hook into our REST APIs should the need arise. | The proposed layout is that the index file and other basic content resides at the root, with REST APIs being in a api/ directory. For example, the app 'toolfoo' might be found at http://server/toolfoo/ and its APIs at http://server/toolfoo/api/. Keeping a consistent approach will allow other applications to easily find and hook into our REST APIs should the need arise. | ||