Expose use of the event loop

The use of the event loop where previously hidden
in internal deep places of the websocket modules.

This commits enforce the client of the library to
explicitely tell what event loop must be used.
This has 3 effects:
 - you know that the systemd event loop is used
 - you tell the event loop to use (no confusion)
 - you don't depend on afb-common.c

Change-Id: Id13d8a96f981183c299cde414d9bb0cd77fe3daa
Signed-off-by: José Bollo <jose.bollo@iot.bzh>

1 files changed, 4 insertions, 2 deletions

diff --git a/src/afb-ws.c b/src/afb-ws.c
index 34796818..53fb60ae 100644
--- a/src/afb-ws.c
+++ b/src/afb-ws.c
@@ -135,10 +135,12 @@ static int io_event_callback(sd_event_source *src, int fd, uint32_t revents, voi
  * Creates the afb_ws structure for the file descritor
  * 'fd' and the callbacks described by the interface 'itf'
  * and its 'closure'.
+ * When the creation is a success, the systemd event loop 'eloop' is
+ * used for handling event for 'fd'.
  *
  * Returns the handle for the afb_ws created or NULL on error.
  */
-struct afb_ws *afb_ws_create(int fd, const struct afb_ws_itf *itf, void *closure)
+struct afb_ws *afb_ws_create(struct sd_event *eloop, int fd, const struct afb_ws_itf *itf, void *closure)
 {
 	int rc;
 	struct afb_ws *result;
@@ -164,7 +166,7 @@ struct afb_ws *afb_ws_create(int fd, const struct afb_ws_itf *itf, void *closure
 		goto error2;
 
 	/* creates the evsrc */
-	rc = sd_event_add_io(afb_common_get_event_loop(), &result->evsrc, result->fd, EPOLLIN, io_event_callback, result);
+	rc = sd_event_add_io(eloop, &result->evsrc, result->fd, EPOLLIN, io_event_callback, result);
 	if (rc < 0) {
 		errno = -rc;
 		goto error3;