Embeddable Common-Lisp

On Tue, 6 Sep 2011 09:59:32 -0400
Matthew Mondor <mm_lists@...> wrote:

> To test, simply change the options at the bottom of test-httpd.conf
> (particularily the default vhost and address/port to bind).  There also
> are debug options/features at the top (note that :beep is
> NetBSD-specific though).  Then:

I obviously meant test-httpd.lisp, not .conf.  I also forgot to mention
about (server:log-tail) which will show the log, (server:log-clear) to
clear it, and (server:log-line fmt &rest args) can be used to add
logging.
-- 
Matt

On Tue, Sep 6, 2011 at 3:59 PM, Matthew Mondor <mm_lists@...:

> The other problem, which I only discovered yesterday night when testing
> the first dynamic application appears to be unicode related: In the
> test application many messages can be entered of various length and
> everything is fine.  Yet if I start copy-pasting UTF-8 from
> UTF-8-demo.txt
> (http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt) then
> eventually the whole document isn't sent anymore, with the browser
> waiting for it to finish loading but it doesn't (a partial page
> results)
>

Hi Matthew, I have not been able to reproduce the crashes yet, but I solved
this problem. The value that you compute as "content-length" in the http
header is the number of lisp characters, not the number of bytes in the
utf-8 encoding. When I changed it to compute the length of the encoded
string, then the server worked perfectly (it is very nice and feels very
snappy indeed!)

I will continue investigating the other stuff.

Juanjo

-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com

On Thu, 8 Sep 2011 19:26:13 +0200
Juan Jose Garcia-Ripoll <juanjose.garciaripoll@...> wrote:

> Hi Matthew, I have not been able to reproduce the crashes yet, but I solved
> this problem. The value that you compute as "content-length" in the http
> header is the number of lisp characters, not the number of bytes in the
> utf-8 encoding. When I changed it to compute the length of the encoded
> string, then the server worked perfectly (it is very nice and feels very
> snappy indeed!)

Oh!  A definite bug on my part :) thank you very much as I didn't
notice this at all.  So I should encode the output first for UTF-8
mode, then actually send bytes rather than characters.

> I will continue investigating the other stuff.

I unfortunately couldn't yet test with various boehm-gc versions as you
had suggested in an off-list post.  I have some homework to do here.
But since I could reliably get the same gdb backtrace it seems to be
involved.

Thanks again,
-- 
Matt

On Thu, 8 Sep 2011 20:54:55 -0400
Matthew Mondor <mm_lists@...> wrote:

> > Hi Matthew, I have not been able to reproduce the crashes yet, but I solved
> > this problem. The value that you compute as "content-length" in the http
> > header is the number of lisp characters, not the number of bytes in the
> > utf-8 encoding. When I changed it to compute the length of the encoded
> > string, then the server worked perfectly (it is very nice and feels very
> > snappy indeed!)
> 
> Oh!  A definite bug on my part :) thank you very much as I didn't
> notice this at all.  So I should encode the output first for UTF-8
> mode, then actually send bytes rather than characters.

So I commited a fix this morning for that part, and it works like a
charm.  The encoding is now provided as a keyword symbol rather than as
a string as well.
-- 
Matt