Sorry, I did not mean to say that your hack would not solve my problem. It's just that I wanted a really simple way to stop the server, that's it. What I tried myself was to create a handler for a stop-server, but that did not work because the variable where I stored the server object seemed to be empty. Maybe that is because the server never returns on a single thread SBCL?
2008/7/12, Anton Vodonosov avodonosov@yandex.ru:
Hm.. My example is ready to use, just download the code. Stopping the server is also included...
on Saturday, July 12, 2008, 2:39:43 AM Mathias wrote:
Cool! I might even try that out :) Still I would like to know if there is any way to stop the Hunchentoot server. That would be enough for most purposes although not as convenient as under SBCL on GNU/Linux.
Anyway, thanks for the link, I will look into it.
/Mathias
On Thu, Jul 10, 2008 at 9:03 PM, Anton Vodonosov avodonosov@yandex.ru wrote:
Hello.
There is a very interesting article about how to use Hunchentoot + Slime in single threaded lisp here: http://avodonosov.blogspot.com/2008/01/it-is-problematic-at-first-sight-to-u...
Although it works better with Clisp on Windows because SBCL doesn't close sockets.
Best regards, -Anton
on Thursday, July 10, 2008, 6:13:47 PM Mathias wrote:
Hi!
I have got SLIME + SBCL + Hunchentoot working on Windows XP, serving a small web app. I also access a small SQLITE database via CLSQL, which works too. All is well but the fact that once I started Hunchentoot from within SLIME, it locks up SLIME. I assume this is because there is no thread support in SBCL under Windows. However, I can live with this if only I knew a way to stop Hunchentoot. Then I could evaluate whatever new or changed stuff on the REPL and then start the server again. I tried C-c C-c (Interrupt Command) but that killed SLIME and SBCL).
Any hints?
/Mathias _______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel