W3C home > Mailing lists > Public > public-interledger@w3.org > January 2017

Re: Interledger HTTP specification proposal

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Mon, 23 Jan 2017 12:07:18 +0100
Message-ID: <CAKaEYhL2EsK_xbAF=2fFT5m7zf00MWX0qsPYoJhMtnnZvsvzrg@mail.gmail.com>
To: Andrew Bransford Brown <andrewbb@gmail.com>
Cc: Adrian Hope-Bailie <adrian@hopebailie.com>, Roberto Santacroce Martins <r@bravado.com.br>, Anders Rundgren <anders.rundgren.net@gmail.com>, Interledger Community Group <public-interledger@w3.org>
On 23 January 2017 at 01:40, Andrew Bransford Brown <andrewbb@gmail.com>
wrote:

> This can handle low-level contract events with sufficient granularity for
> stocks, bonds, currencies, etc:
>
>
> POST /cgi-bin/transactionEvents.cgi HTTP/1.1
>
> User-Agent: Interledger/1.0
> Content-Type: text/plain
> Content-Length: 7
> IL-TransactionID: xyzOrGUID
> IL-CommerceID: IL-CommerceID
> IL-Event-Type: Offer, Terms, Counter-Offer, Accept, Deliver, Complete
> IL-Event-DateTime: YYYY-MM-DD HH:MM:NN.nnnnnn GMT
>
> 100 BTC
>
>
>
> GET /cgi-bin/transaction.cgi HTTP/1.1
>
> IL-TransactionID: xyzOrGUID
>
>
Why not put the details of the message in the body, instead of mixing with
the headers.  HTTP Headers should only be really used for HTTP level stuff,
so that the message can be sent over multiple channels.

<#xyzOrGUID> a Transaction ;
:CommerceID "IL-CommerceID" ;
:Event-Type "Offer, Terms, Counter-Offer, Accept, Deliver, Complete" ;
:timestamp "YYYY-MM-DD HH:MM:NN.nnnnnn GMT"^^xsd:Date ;
:amount 100 ;
:currency <BTC> .
Received on Monday, 23 January 2017 11:07:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 January 2017 11:07:51 UTC