Expose use of the event loop
authorJosé Bollo <jose.bollo@iot.bzh>
Wed, 27 Jul 2016 13:51:01 +0000 (15:51 +0200)
committerJosé Bollo <jose.bollo@iot.bzh>
Wed, 27 Jul 2016 15:40:58 +0000 (17:40 +0200)
commit1ea6bd0f466a10d29f12801aa35fb6d2b30443a1
tree308bbc689182de8cfd9e42f76dea57455d3a5434
parent1d0f869ce3379089b4f4c5285e3d30e971e5b93d
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>
src/CMakeLists.txt
src/afb-client-demo.c
src/afb-ws-client.c
src/afb-ws-client.h
src/afb-ws-json1.c
src/afb-ws.c
src/afb-ws.h
src/afb-wsj1.c
src/afb-wsj1.h
src/export-afbwsc.map