As I am working on a new implementation of the wire protocol in Jaybird,
I occasionally run into things that are not (clearly) documented in the
wireprotocol documentation (src/docs/firebirddocs/wireprotocol.xml).
Are there any objections if I add to or improve on this document?
Mark
--
Mark R
Hi Mark,
> As I am working on a new implementation of the wire protocol in Jaybird,
> I occasionally run into things that are not (clearly) documented in the
> wireprotocol documentation (src/docs/firebirddocs/wireprotocol.xml).
>
> Are there any objections if I add to or improve on this document?
On 31-12-2013 14:33, Paul Vinkenoog wrote:
> Hi Mark,
>
>> As I am working on a new implementation of the wire protocol in Jaybird,
>> I occasionally run into things that are not (clearly) documented in the
>> wireprotocol documentation (src/docs/firebirddocs/wireprotocol.xml).
>>
>> Are there any
Mark Rotteveel wrote:
> >> As I am working on a new implementation of the wire protocol in Jaybird,
> >> I occasionally run into things that are not (clearly) documented in the
> >> wireprotocol documentation (src/docs/firebirddocs/wireprotocol.xml).
> >>
> >> Are there any objections if I add to
On 31-12-2013 17:39, Paul Vinkenoog wrote:
> Mark Rotteveel wrote:
>> Annoyance number one: xmlmind does not use the same linebreak behaviour
>> (which elements get a linebreak after open) and whitespace as the
>> original author (spaces vs tabs). My first commit is going to change a
>> lot of whit
Mark Rotteveel wrote:
> You can configure if XMLmind indents at all, and the number of spaces,
> it unfortunately does not support using tabs instead of spaces. I could
> of course make XMLmind use a relatively large number of spaces and
> replace those with tabs before a commit, but that sounds a
