Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. Re: Initial proposal for Kea Control API (Thomas Markwalder)
----------------------------------------------------------------------
Message: 1
Date: Fri, 15 Jul 2016 14:34:59 -0400
From: Thomas Markwalder <[email protected]>
To: [email protected]
Subject: Re: [kea-dev] Initial proposal for Kea Control API
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hey:
It occurs to me that the requirements do not make any mention of whether
Kea would or should support multiple, concurrent connections to the API
channel. I don't suppose it matters much, as long currently commands
are processed "atomically".
We read a command, carry it out, respond and wait for (go to) the next
one.
I'm not advocating a position on whether Kea should or should not
support multiple command channel connections (yet); I'm asking if it's a
topic we should include in requirements.
Thomas
------------------------------
Subject: Digest Footer
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
------------------------------
End of kea-dev Digest, Vol 28, Issue 6
**************************************
