| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This function allows to connect to an API exported by the
binder.
The demo program afb-client-demo is modified to integrate
on option that direct API connection.
Example:
server: afb-daemon --ws-server unix:hello
client: afb-client-demo -d -H unix:hello
Change-Id: Id9f857a453c406df1c4b36eb25fb5e833a938c3d
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
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>
|
|
afb-common.* files are not public and so not distributed
in any development package. This makes difficult to create
a client with sources out-of-tree.
Change-Id: Ib2edd48f864f55821ab590442efdf6d1e2fdcd58
Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
|
|
This library is intended to be used by C clients to connect
to the binder and access to its fetures through the websocket.
An example of integration is given by afb-client-demo.c
It is known that it introduces an unwanted dependency to afb-common.
This is a temporary issue.
Change-Id: Ie0a395f116f6ee05679525a6399ef23ef245c944
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
José Bollo
Stephane Desneux