use a shorter message format than JSON

[michielbdejong]

JSON is no very efficient as some messages convey only one or a few bits of information. Should consider using a shorter format.

[michielbdejong]

new simplified protocol idea, wth no routing:

• ledgerloops-0.8|c-p|<loopId>|UCR-1|0.1
• ledgerloops-0.8|s-c|<loopId>|<trigger>
• ledgerloops-0.8|p-r|<loopId>
• ledgerloops-0.8|rej|<loopId>
• ledgerloops-0.8|err|<loopId>|<err-code>

Flows:

• -> c-p
  • <- err
  • <- s-c
  • -> ack
  • -> err
  • <- rej
  • -> ack
  • -> err
  • -> p-j
  • <- rej
  • <- err

[michielbdejong]

might do this some day. In the Interledger project, we spent a lot of time (probably too much time) rewriting the protocol syntax, and I would like to avoid that pitfall this time around.

[michielbdejong]

sticking to JSON now, as there's no real reason to bikeshed back-and-forth about such implementation details. The Interledger Project was trying to define a protocol which everybody would start using for unforeseen use cases because of the superiority of that protocol. So there it made more sense to linger on protocol syntax. In the LedgerLoops Project, I'm trying to build an open source software tool and an open network of users, and I think neither developers nor users will care so much what message format is under the hood, as long as it works well.