Dave Challis

VelocyPack format

8

In case it's of any use/interest, I've started work on a Rust implementation of the VelocyPack format in Rust at: https://github.com/davechallis/rust-velocypack It's currently got some basic serialization working, currently working...

Current set is very conservative, initially due to an HTTP path parsing issue in actix-web. This should be resolved now, so re-investigate the options.

Add configuration around dealing with failed connections, e.g. number of retries, wait time between retries, etc.

Feature request: option to display times in 24 hour clock

1

## Requirement - what kind of business use case are you trying to solve? Most of our logs, alerts, etc. show times using a 24h clock. When looking using the...

Suggestion: clarify documentation on how to set Fbm parameters, or make fields private

2

Since `Fbm`'s fields are public, I assumed that the correct way of changing them was just to modify them. This worked for many cases, but then I noticed that I...

Documentation request: clarify padding usage in objects

3

I've been working on a velocypack parser (in Rust), and ran into some troubles parsing some output from ArangoDB: ``` 0x0c 0x73 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x4a...

I'm trying to debug some output returned by the velocystream protocol, which consists of multiple velocypacks (header plus response body). Parsing this with the `vpack-to-json` tool only decodes the first...