Prince Riley pisze:
Since the discussion in this thread has advanced pretty far along
toward recommending a FP and Powtils solution to you, then it appears
you have a technical answer from the group you can explore.
However, without suggesting there is a bias in favor of a specific
client-centric vs server-centric web framework, the REST protocol has
succeeded in becoming a paradigm for writing web (client sever) apps.
Primarily the reason why is -- especially for DB web applications --
is efficiency, maintainability, and scalability. The recent major
efforts by Mozilla, Google, and others to improve the performance of
browser Javascript engines is due to their experience designing,
writing and running CGI based web applications. There is quite a bit
of literature and discussion on the web explaining why they are using
REST versus CGI (Request/Response) which you might find helpful in
making your design choices.
REST is bad choice for application , especially for this with much
interaction with DB. REST is stateless. Are You see any desktop
application, which is stateless?
REST is good for simple catalogs, list of parts, etc. For sophisticated
application this architecture has many limitation. Most of view depend
of before user actions.
--
Darek
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
