<div><div>Hi. I'm somewhat new to Scheme, but not a complete newbie. I've gone</div><div>through HtDP and read many parts of the Guide and Reference that come</div><div>with PLT Scheme. In practical terms, I'm reasonably comfortable with</div>
<div>writing small to mid-sized programs with PLT, like command-line</div><div>utilities, games and the like.</div><div><br></div><div>Currently, I'm in the process of developing a web app to run on the</div><div>PLT web server. The main benefit for me is the fine-grained control</div>
<div>supplied by the continuation-based framework, which allows me to think</div><div>as if I was doing "regular" programming (no inversion of control</div><div>because of HTTP).</div><div><br></div><div>I've seen (and implemented on my on) many of the examples I could</div>
<div>find, which means:</div><div><br></div><div>1) The blog app from the "Continue" tutorial;</div><div>2) ListIt, by Jens Axel Søgaard;</div><div>3) pltwitter.plt, by Jay McCarthy</div><div><br></div><div>They are all fine examples, but aren't enough to give me a feeling,</div>
<div>for instance, how I should structure code that will be deployed to</div><div>production.</div><div><br></div><div>For instance, the blog app and ListIt (as shown in MacCarthy's blog)</div><div>all produce html, using xexpr format, straight from the controller</div>
<div>code. In principle I have nothing against it, but I suspect that for</div><div>big applications it wouldn't work so well. Besides, one can't easily</div><div>output doctypes using the standard xexpr only, and the code is not</div>
<div>"pretty-print" in the browser. I was able to find a way around the</div><div>doctype issue using tips from the following posts:</div><div><br></div><div><a href="http://www.topmost.se/personal/articles/web-programming-with-plt-scheme/serving-xhtml.htm">http://www.topmost.se/personal/articles/web-programming-with-plt-scheme/serving-xhtml.htm</a></div>
<div><a href="http://www.topmost.se/personal/articles/web-programming-with-plt-scheme/custom-dispatchers.htm">http://www.topmost.se/personal/articles/web-programming-with-plt-scheme/custom-dispatchers.htm</a></div><div><br>
</div><div>Anyways, for bigger application I'm sure it would be better to use</div><div>templates, but still have some questions.</div><div><br></div><div>* In practical terms, how do I use apache with the plt-web-server?</div>
<div> Should I just proxy the requests or use apache to serve static files</div><div> too? I suspect apache's performance is better for static files, but</div><div> don't have means to know if the added complexity (in terms of</div>
<div> configuration) pays off.</div><div><br></div><div>* Are there any bigger open source web apps written for PLT that you</div><div> can point me to?</div><div><br></div><div>* Are there any practical guides on how to deploy an application to</div>
<div> production? It seems the server can be configured in many different</div><div> ways, and that's a good thing. On the other hand, as a beginner, I</div><div> feel overwhelmed with so many options.</div><div><br>
</div><div>* Are there any connection-pool-style packages that let me connect to</div><div> PostgreSQL with minimal hassle?</div><div><br></div><div>* How well do JQuery, prototype, and the like, fit together with Scheme </div>
<div> code?</div><div><br></div><div>Thanks from Brazil,</div><div><br></div><div>Reginaldo</div></div>