On Tue, Jun 14, 2016 at 02:00:14 +0200, Tobias Hunger wrote:
> Implementing new Protocol Versions:
> ==
> Deprecating old Protocol Versions:
>
One idea that came up on a previous project was the following:
namespace protocol {
Hi Brad,
Am 17.06.2016 22:24 schrieb "Brad King" :
>
> On 06/13/2016 08:00 PM, Tobias Hunger wrote:
> > * There will always be 1 client talking to a server.
> > * Client/Server communicate using JSON messages
>
> Yes. IIRC it is using stdin/stdout (I haven't checked the
On 06/13/2016 08:00 PM, Tobias Hunger wrote:
> * There will always be 1 client talking to a server.
> * Client/Server communicate using JSON messages
Yes. IIRC it is using stdin/stdout (I haven't checked the code),
so limiting to one client is implicit.
In this case, is it actually a daemon?
PS: I think it would make perfect sense to ship the first cmake version with
included daemon-mode with a big, fat warning that the interfaces are not
finalized yet and will change in incompatible ways during the first release
cycle (or maybe two:-).
In my experience you only get the full feedback
Hello,
one important piece of feedback from the daemon-mode: Project
structure discussion is that we need a policy to remove old code
again.
So I thought I should write up a bit about the infrastructure and
versioning support of the daemon-mode branch I am working on.
Basic Assumptions: