> Looks like you specified reaching the SCGI server via a Unix domain > socket, but you never told the Racket program to use that socket. You > actually can't use that kind of socket with the Racket SCGI library -- > typically, the SCGI server will talk TCP to localhost on a specific port. > > Offhand, I can't tell you confidently the exact lighttpd configuration to > use, since the lighttpd SCGI module appears not clearly documented, but you > can figure it out from: > http://redmine.lighttpd.net/projects/1/wiki/Docs_ModSCGI >
Thanks for answer, I will study Lighttpd doc more, but on this subject it seems to me a little vague. In the meantime I will use standard CGI. Response time to scripts in racket/base language are satisfactory for local use. (I wonder if pointing to compiled scripts will make a noticeable difference, I have to try). When I will need more performance if I can not find a way with lighttpd I will try Apache or Nginx. Please let me explain why I think CGI are a useful approach even if more advanced tools for web application are already available in Racket: Consider the opportunity to have a directory in your workstation's home full of subdirectories with a number of potentially almost independent, reusable, well documented, simple little scripts. You can use them from your browser to make almost anything (from managing your system, to your data, to making graphics programs, to forge code editors...) using all the power of Racket, and this collection can grow organically over time without or with little previous planning. Scripts can be easily made to interact, just like functions. Complex systems will pop-up in short time. I happily used Lua in the past to do all this. But Racket can serve me better of an order of magnitude. Xexpr's obviously are a fantastic option to make all sorts of HTML user interfaces without touching a line of HTML. CSS can be also programmatically generated or use statically to alter "GUI" as you like with great versatility in every development phase. I personally dislike JS, despite all the time I played with Node... But used sparingly can be very useful in such a system. Some pre-made ajax helper functions used well can do wonders. Forgive me to state the obvious: web-applications are very useful. But, the need to make enormous preplanned apps, or run a thousand independent Racket server to achieve what I want is something I can escape with CGI. Thanks for attention. Lux -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
