One further point in this thread ... As a starting point in your thinking thru the design choices, here is a fairly complete but accessible article on the topic you might find helpful <br><br><a href="http://www.ibm.com/developerworks/java/library/wa-ajaxarch/index.html">http://www.ibm.com/developerworks/java/library/wa-ajaxarch/index.html</a><br>
<br><br><div class="gmail_quote">On Tue, Mar 3, 2009 at 12:30 PM, Prince Riley <span dir="ltr"><<a href="mailto:wmarketing3@gmail.com">wmarketing3@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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. <br><br>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. <br>
<br>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. <br>
<br>I have not worked with Powtils so I can't discuss whether or not it has the features your application needs, or what the costs of using it might be in terms of server processing load (Web server Request/Response), response time, DB transaction processing load, etc. I also don't know whether it can be tweaked in some way to support the REST protocol for an application like yours. <br>
<div><div></div><div class="Wj3C7c">
<br><br><div class="gmail_quote">On Mon, Mar 2, 2009 at 3:16 PM, Francisco Reyes <span dir="ltr"><<a href="mailto:lists@stringsutils.com" target="_blank">lists@stringsutils.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Prince Riley writes:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Finally, give the advance from CGI based web apps to Web 2.0 (Javascript running in the browser) is there a design rational for running code on the server instead of in the web browser.<br>
</blockquote>
<br></div>
I think that is almost a religious war type of discussion...<br>
Short answer (as it applies to me at least) If all I am doing is getting data from a DB and displaying it in the browser, there is little reason to do Javascript. <br><div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
past few years. Zend (which is PHP, not Javascript) is also an alternative. <br>
</blockquote>
<br></div>
Personally my preference would be<br>
1- Pascal<br>
2- Python<br>
3- PHP<br>
<br>
PHP can do absolutely everything I need/want; the difference is that I want something which lends itself more easily to well organized and structured coding. Also When I work on php it always feels like work.. even if it something I am doing for fun. It is one of those subjective things... the reason why there are so many languages and tools out there. _______________________________________________<div>
<div></div><div><br>
fpc-pascal maillist - <a href="mailto:fpc-pascal@lists.freepascal.org" target="_blank">fpc-pascal@lists.freepascal.org</a><br>
<a href="http://lists.freepascal.org/mailman/listinfo/fpc-pascal" target="_blank">http://lists.freepascal.org/mailman/listinfo/fpc-pascal</a><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>