proto: correct a few comments dating to an earlier version of this

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
Peter Hutterer 2022-02-21 11:11:44 +10:00
parent 3f97bacd21
commit 44b986daec

View file

@ -31,14 +31,7 @@ syntax = "proto3";
* The server may send DeviceRemoved for a device at any time.
*
* Where a connection error occurs, the library (libei or libeis) will
* unroll the state as seen from the API. i.e.
*
* Due to the server's ability to modify input device capabilities, the
* initial requests cannot be batch-processed. Specifically: The AddDevice
* request (3.) requires the EIS library implementation to query the caller
* for the response. Until the caller performs the action (and this may
* including waiting for user confirmation), libeis must discard any events
* coming from the client for this device.
* unroll the state as seen from the API.
*
* Pre-configuring a connection
* ----------------------------
@ -49,9 +42,7 @@ syntax = "proto3";
* then pass the fd to the client to create a libei context from that.
*
* The proxy can force a client name and/or restrict other options. This is
* transparent to the client, it doesn't know what restrictions are in place
* until it runs up against them (e.g. a device with a restricted capability
* will not be added with that capability).
* invisible to the client, it does not know what restrictions are in place.
*
* Configure messages may come at any time but they can only ever *reduce*
* the current capabilities, not increase them.