This encoder/decoder is based on Alex's rosetta example
https://bitbucket.org/hsarvell/ext/src/31f26bbff901e1a88aa997ce919b7edb50ea810d/json.l?at=defaultbut
has turned out quite changed to automatically account for various edge
cases.

With this CURL based client you can post the JSON straight in the body of
the HTTP message:
https://bitbucket.org/hsarvell/ext/src/31f26bbff901e1a88aa997ce919b7edb50ea810d/client.l?at=default

Pl-web also recently started to support consuming a "raw" JSON POST body on
the server by way of the *Body global:
https://bitbucket.org/hsarvell/pl-web/commits/a710a5e934b669f859963c36b6c8b020f2fdee0c




On Tue, Feb 18, 2014 at 3:45 AM, Rick Lyman <lyman.r...@gmail.com> wrote:

> Look at this post:
> http://blog.gmane.org/gmane.lisp.picolisp.general/month=20121001.
>
> For session management you may want to look at:
> http://picolisp.com/wiki/?macropis.
>
>
>
>
> On Mon, Feb 17, 2014 at 1:44 PM, klaus schilling 
> <schilling.kl...@web.de>wrote:
>
>> hello,
>> is it possible to write a client for a JSON rest service in picolisp?
>>
>> Many services abandon their XML-RPC API and flee to JSON rets, for
>> whatever reason.
>>
>> Klaus Schilling
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
>

Reply via email to