This post originated from an RSS feed registered with PHP Buzz
by Alan Knowles.
Original Post: dmdscript with fastcgi
Feed Title: Smoking toooo much PHP
Feed URL: http://www.akbkhome.com/blog.php/RSS.xml
Feed Description: More than just a blog :)
I've been slowly ticking away adding features to the gtk javascript bindings, in doing so, I'm adding extra libraries - Mysql works quite well, and Seeing the recent post on planet.dprogramming.com about fastcgi4d, I wondered if I could run dmdscript from fastcgi.
To enable a web version of dmdscript with my bindings, I had to do quite a bit of re-organization, enabling it to be built with random libraries added in and exclude the Gtk stuff. Core to this was to move all the registration code into the directories that hold the binding code. Each binding directory now contains 3 files, binding***.d, binding***type.d and register***.d. Which manage the dynamic loading of .so (or .dll if windows actually works). and the registering of all the javascript objects and methods.
For fastcgi, I had a look at the code described on the blog post, but was very reluctant to use it, as it
required tango, which is not a current requirement, and I'm a little concerned about using.
required knowlege of templates, which are still a bit of a black art. and I've only used very sparingly when absolutly every other alternative has been ruled out.
So after considerable digging through the code and trying to make head or tail of the code on fastcgi.com, I finally found the python fastcgi code, which ported easily to D.
The core files libraries that are helpers in dealing with fastcgi are here. http://www.akbkhome.com/svn/gtkDS/src/fastcgi/
They need the loader.d and paths.d file from here http://www.akbkhome.com/svn/gtkDS/wrap/ to be usable.
and the current, non-threaded simple responder is here http://www.akbkhome.com/svn/gtkDS/src/fcgi.d
So for hello world example, this simple piece of code dumps all the server variables and says hello world.
println(Request.toSource());
println("hellow world from javascript");
Next job is to look at how GET/POST data is passed around and how to escape data on output. among a list of 100 ideas for how it could all work.
Previous Topic
