On Wed, Mar 22, 2006 at 11:32:17PM -0700, Shawn Rutledge wrote: > I found that in the latest version I got an error like this: > > Error: call of non-procedure: "./web" > > Call history: > ... > <eval> (load "/etc/spiffy-conf.scm") > <eval> (spiffy-root-path "/var/www/localhost/htdocs") <-- > > whereas if I set! spiffy-root-path it works. Was it intentional to > quit using parameters and have them be plain variables? I'm curious > if there is a reason why using parameters was bad?
Blame me :) Implementing an on-the-fly reloadable config file is only possible if you can make all threads aware of the changed options. Parameters are meant to be thread-local, so there's no way to update all threads. Also, there's no way to control which thread handles a signal (I use SIGHUP as the signal to instruct Spiffy to reload the configuration). This is also the reason I decided to update Spiffy's version to 2.0, with the idea that a major version increase communicates a warning that the API has changed in a backward-incompatible way. Of course, we could go back to parameters if anyone has a suggestion how to implement dynamic reconfiguration with them. I decided to add dynamic reconfiguration after adding vhost support, since it is annoying to have to restart the server every time you add a new virtual host. It is also beneficial if you want to change the filetype map or the index page pattern, for example. Regards, Peter -- http://www.student.ru.nl/peter.bex -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth
pgpSTdcFLxnqa.pgp
Description: PGP signature
_______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users