> From: Lassi Kortela <xxxxxx@lassi.io>
> Date: Monday, September 30, 2019 9:29 AM
>
> [ We'll do a pure Java to JDBC implementation. ]

>> Another question is subprocess and/or wire (net) protocol, I'll leave
>> that to you.  I already have one net connector with PostgreSQL, so my
>> gaining experience sooner with your subprocess method would be good.

Based on the change of the Subject: line, you want to do it through a
subprocess connector?  Sounds good.

> Let's use the core binary format that this project is crafting,
> whether it's an ASN.1 subset or a varint based thing. I see no reason
> for the extra hazards of text since it's machine-to-machine
> communication, and using a tailor-made format instead of a generic one
> would soon paint us into a corner when it's time to make extensions
> and improve tooling.

I haven't had the mind bandwidth to follow that part of our project.

Can the binary format be implemented by generic R6RS/R7RS-small
implementations?  Are the hazards of text so great they outweigh the
presumed advantages for debugging, i.e. using a serialization library
which allows transparent use of either?

> Apart from the encoding though, we could work together to evolve the
> vocabulary (i.e. which messages are sent). The encoding and the vocab
> are completely decoupled from each other, so they can evolve
> independently. My idea for the vocab is to track your Scheme API as it
> evolves, diverging as little as possible :)

Yeah, that's the major task for me for this, and will be a while in the
future, we've got a lot of APIs to design or perfect.

- Harold