Hi Henrik,
Content-Length: 477
Accept-Encoding: gzipX-Hub-Signature:
sha1=c22189670d1aeb04d0333d737b3e97f74ccb380e
User-Agent: AppEngine-Google; (+http://code.google.com/appengine)
Host: localhost:3000
Referer: http://localhost/
Content-Type: application/atom+xml
And the feed contents
I just noticed that someone had searched for picolisp json on
Google, I've attached the JSON encoder/decoder to this mail.
However there is one problem, it isn't properly managing when there
are complex texts involved, then the double quote escaping might get
it wrong if there are already escaped
Wow. That's the first time I've gotten a response from a mailing list by
merely googling for an answer--and faster than sometimes when I've asked
directly, too. Impressive. :)
I was enjoying messing around with PicoLisp, and wanted to know what the
library situation looked like for some key
I use the JSON library extensively on vizreader.com so I know it works
for most things, actually the text I mentioned before that broke it
contained javascript inside it I think.
As for the tag stripping I'm actually only using PHP-cli for all my
needs at the moment, leaving Ruby out of the
I've done some more examining and testing and I think the content
might be chunked even though there's nothing advertised in the
headers.
Alex, you mentioned on IRC how to handle/read chunked content and of
course I forgot to save the buffer. Would you care to go through it
again please?
I also
Hi Henrik,
Alex, you mentioned on IRC how to handle/read chunked content and of
course I forgot to save the buffer. Would you care to go through it
again please?
This is fairly easy, when you use the functions 'ht:Out' and 'ht:In':
(ht:Out T .. do printing ..)
does chunked output, and