I am thinking of creating a standalone web application.
Im architecture considers the following:
Web server (remote) ↔ Web server / cache (local) ↔ Browser / Prism
Benefits for this model:
- Deployment is based on the Internet, with all the benefits of this approach.
- Offline support
- UI synchronization (html / js) is not a problem
- Data synchronization can be mostly automated.
- while I stay within the framework of the RESTful paradigm
- I can break this down as needed, but manual synchronization will basically remain surgical.
- The local web server starts as a service; I can run arbitrary code, including data synchronization overs
- I have full control over the data (location, lack of size restrictions, lack of the ability to delete a user unknowingly).
- Prism with extension may allow to keep closed javascript source
Any thoughts on this architecture? Why should I / should not use it? I am especially looking for success / horror stories.
Long version
Notes:
- Users are not very computer. For example, even superficially explaining how Gears works is completely out of the question.
- I will be responsible if the data is lost, even if it is really a user error (except that it deletes random directories on his machine).
- I can require users to install something on their computer. It should not be 100% web and / or run in a sandboxed environment.
. .
Gears/HTML5:
- ,
.
- (
)
- ;
- -, .
- , sql ( , sql , ). .
- (html/js)
Adobe AIR:
:
- - ().
,
.
- (). ( ).
- (). Im .
- ( ). , . , . , , , . , , - .
user122122