Server Internals

These are only called by the platform-specific mainloop polling code. More...

Collaboration diagram for Server Internals:

Functions
xrt_result_t	ipc_server_get_system_properties (struct ipc_server *vs, struct xrt_system_properties *out_properties)
void	ipc_server::ipc_server_handle_client_connected (struct ipc_server *vs, xrt_ipc_handle_t ipc_handle)
	Called when a client has connected, it takes the client's ipc handle. More...
void	ipc_server::ipc_server_handle_failure (struct ipc_server *vs)
	Perform whatever needs to be done when the mainloop polling encounters a failure. More...
void	ipc_server::ipc_server_handle_shutdown_signal (struct ipc_server *vs)
	Perform whatever needs to be done when the mainloop polling identifies that the server should be shut down. More...

Detailed Description

These are only called by the platform-specific mainloop polling code.

Function Documentation

ipc_server_handle_client_connected()

void ipc_server_handle_client_connected	(	struct ipc_server *	vs,
		xrt_ipc_handle_t	ipc_handle
	)

Called when a client has connected, it takes the client's ipc handle.

Handles all things needed to be done for a client connecting, like starting it's thread.

Parameters

vs	The IPC server.
ipc_handle	Handle to communicate over.

References os_mutex::os_mutex_lock().

ipc_server_handle_failure()

void ipc_server_handle_failure

(

struct ipc_server *

vs

)

Perform whatever needs to be done when the mainloop polling encounters a failure.

ipc_server_handle_shutdown_signal()

void ipc_server_handle_shutdown_signal

(

struct ipc_server *

vs

)

Perform whatever needs to be done when the mainloop polling identifies that the server should be shut down.

Does something like setting a flag or otherwise signalling for shutdown: does not itself explicitly exit.