> -----Original Message----- > From: Laatz, Kevin > Sent: Thursday, October 11, 2018 9:58 AM > To: [email protected] > Cc: Van Haaren, Harry <[email protected]>; > [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; Richardson, Bruce > <[email protected]>; Ciara Power <[email protected]>; Brian > Archbold <[email protected]>; Laatz, Kevin <[email protected]> > Subject: [PATCH v4 05/13] telemetry: add client feature and sockets > > From: Ciara Power <[email protected]> > > This patch introduces clients to the telemetry API. > > When a client makes a connection through the initial telemetry > socket, they can send a message through the socket to be > parsed. Register messages are expected through this socket, to > enable clients to register and have a client socket setup for > future communications. > > A TAILQ is used to store all clients information. Using this, the > client sockets are polled for messages, which will later be parsed > and dealt with accordingly. > > Functionality that make use of the client sockets were introduced > in this patch also, such as writing to client sockets, and sending > error responses. > > Signed-off-by: Ciara Power <[email protected]> > Signed-off-by: Brian Archbold <[email protected]> > Signed-off-by: Kevin Laatz <[email protected]> > ---
Acked-by: Harry van Haaren <[email protected]>
