Hi,
I'm back from vacation and am now integrating 0.5.2 into my main code base. This so I can make use of the Araneida and standalone TBNL.
It didn't work.
I got it to work by changing how *use-modlisp-headers* is used. I've attached a patch. I think you must have changed how I was using it while cleaning up the patch I sent originally.
Cheers, Bob
---- Bob Hutchison -- blogs at http://www.recursive.ca/hutch/ Recursive Design Inc. -- http://www.recursive.ca/
Hi Bob!
On Fri, 1 Apr 2005 17:03:07 -0500, Bob Hutchison hutch@recursive.ca wrote:
I'm back from vacation and am now integrating 0.5.2 into my main code base. This so I can make use of the Araneida and standalone TBNL.
It didn't work.
I got it to work by changing how *use-modlisp-headers* is used. I've attached a patch. I think you must have changed how I was using it while cleaning up the patch I sent originally.
Yes, I changed some things but I tested with all three setups afterwards. What exactly doesn't work for you?
Cheers, Edi.
On Apr 1, 2005, at 5:47 PM, Edi Weitz wrote:
Hi Bob!
On Fri, 1 Apr 2005 17:03:07 -0500, Bob Hutchison hutch@recursive.ca wrote:
I'm back from vacation and am now integrating 0.5.2 into my main code base. This so I can make use of the Araneida and standalone TBNL.
It didn't work.
I got it to work by changing how *use-modlisp-headers* is used. I've attached a patch. I think you must have changed how I was using it while cleaning up the patch I sent originally.
Yes, I changed some things but I tested with all three setups afterwards. What exactly doesn't work for you?
The TBNL stand-alone. When it was writing the headers it had the wrong value for *use-modlisp-headers* -- value of t rather than nil. Consequently it was returning mod_lisp stuff to the browser and the browser, naturally enough, didn't like it.
Cheers, Edi.
---- Bob Hutchison -- blogs at http://www.recursive.ca/hutch/ Recursive Design Inc. -- http://www.recursive.ca/
On Fri, 1 Apr 2005 17:50:26 -0500, Bob Hutchison hutch@recursive.ca wrote:
The TBNL stand-alone. When it was writing the headers it had the wrong value for *use-modlisp-headers* -- value of t rather than nil. Consequently it was returning mod_lisp stuff to the browser and the browser, naturally enough, didn't like it.
Did you set it to NIL manually before using it?
http://weitz.de/tbnl/#tbnl-start
Cheers, Edi.
On Apr 1, 2005, at 5:58 PM, Edi Weitz wrote:
On Fri, 1 Apr 2005 17:50:26 -0500, Bob Hutchison hutch@recursive.ca wrote:
The TBNL stand-alone. When it was writing the headers it had the wrong value for *use-modlisp-headers* -- value of t rather than nil. Consequently it was returning mod_lisp stuff to the browser and the browser, naturally enough, didn't like it.
Did you set it to NIL manually before using it?
Ah, now I see. I wanted to be able to run any of the combinations at the same time. Setting the value of *use-modlisp-headers* will prevent that -- that will force a choice between direct and indirect. The patch I sent uses the test in read-http-request to set the value of *use-modlisp-headers*.
Cheers, Edi.
---- Bob Hutchison -- blogs at http://www.recursive.ca/hutch/ Recursive Design Inc. -- http://www.recursive.ca/
On Fri, 1 Apr 2005 18:15:48 -0500, Bob Hutchison hutch@recursive.ca wrote:
Ah, now I see. I wanted to be able to run any of the combinations at the same time. Setting the value of *use-modlisp-headers* will prevent that -- that will force a choice between direct and indirect. The patch I sent uses the test in read-http-request to set the value of *use-modlisp-headers*.
Yes, I remember that now - makes sense. Don't know why I changed that. I'll prepare a new release with updated docs this weekend.
Cheers, Edi.
-
Bob Hutchison -
Edi Weitz