Age | Commit message (Collapse) | Author |
|
|
|
|
|
If we are going to use batteries for numeric_compare, why not take
advantage of the rest.
|
|
|
|
Right now it uses a SHA-1 sum of 30 random bits. I hope that's secure enough.
|
|
The Message module contains read and write functions that take care of
the wire protocol, which sends a 4 byte length header before every message.
They take a bytes buffer and don't care about its contents.
The Vyconf_client module has high level functions for interfacing with vyconfd.
Functions for creating a socket and creating a server loop are in Startup.
The rest is, for now at least, right in vyconfd.
Notes:
Message.read/write probably should be wrapped in Lwt_io.atomic
We need to find out if it's safe to reuse Pbrt.Encoder.t or we really
should create it every time.
|
|
|
|
|
|
validators.
What's bad is that right now way too many things are aware of the nature of external validators,
and the validators dir (formerly validators hashtable) is passed around a lot.
We'll need to think it through.
|
|
Use of the Result module from a compatibility library came from using Yojson
for config parsing, which uses it for compatibility with older OCaml, since
the ('a, 'b) result type appeared in Pervasives only in OCaml 4.03
All projects using vyconf library, however, by definition will be new projects,
and will not have any reasons to use older compilers.
|
|
|
|
|
|
|
|
|
|
|
|
|