Age | Commit message (Collapse) | Author | Files | Lines |
|
This solves issues encountered when starting
remote services. It delays all services until
completion of network initialisation. Delaying
every services is not selective. Further
optimisation may improve that issue.
Bug-AGL: SPEC-1650
Change-Id: I5742a4cd514c86c724a8e7a86c7e0a5dde6a8c67
Signed-off-by: Jose Bollo <jose.bollo@iot.bzh>
|
|
Forbids exportation of service apis for
apis that are not exported as 'ws' or 'auto'.
Bug-AGL: SPEC-1650
Change-Id: I0681bdb0632d9f331036abc1ff1e1b2bb37933cd
Signed-off-by: Jose Bollo <jose.bollo@iot.bzh>
|
|
This commit introduce "tcp", a new type of
provided/required api. It appears in the config.xml
as below:
<urn:AGL:widget:provided-api>
<param "name"="HOST:PORT/API" "value"="tcp">
<urn:AGL:widget:required-api>
<param "name"="HOST:PORT/API" "value"="tcp">
This implementation is a draft. The service
exposed can not start automatically. Use it
with the permission urn:AGL:permission::system:run-by-default.
Change-Id: Ic593f0d891692ca0c777c49057ec54c37fc55cc0
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Forcing symbolic link update ensures that if the value changes
the link will be overwriten. Otherwise the link always
keeps the old path until a system reboot or a manual removal
of the link file.
Change-Id: Ib9d8f267a8665edd75ce04f77eb70c4b0a4b8e9f
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
This commit introduce two new features:
<urn:AGL:widget:provided-binding>
<param "name"="public-name" "value"="relative-path-to-the-binding"/>
<urn:AGL:widget:required-binding>
<param "name"="public-name" "value"="extern">
<param "name"="relative-path-to-the-binding" "value"="local">
TODO: manage security by setting correct Smack label to the exported files
Bugs-AGL: SPEC-1439
Bugs-AGL: SPEC-1663
Change-Id: I70aad7d523ece7a2ae0058b79708a02ef81144e2
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Before this change, APIs were only provided as binder's
exported websockets. This forbade ability to use symbolic
links.
Allowing links is interesting for having platform sockets
and for linked api (not using socket).
The API afm-main is a platform API. It must run at system level
and must be available for all user clients. To achieve it, we
use a link.
Bug-AGL: SPEC-1592
Change-Id: I8753f83373755eb7fc2d2cc50251b8f738b61b03
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: Ib6ba886df110d8a23e3760e1818263ec757b9c7c
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: I53d3cac7136e4d169acd8e3e3de5ea8439dd0192
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: Ia4ef2a6e3c07616ccd756933a82f0806844c4faf
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
2 new configuration variables:
- afm_platform_rundir (default /run/platform)
Path to location of platform runtime sockets
- afm_users_rundir (default /run/user)
Path to location of users runtime sockets
Change-Id: I65007fee1ca2ce6f1247a67ba0b121f97c08f209
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
The Smack permission to write on the websocket of the API
must be set to something that allows the communication!
Here the chosen value is *
Change-Id: Ia276219b232e33bd35353d8feb333513b340e75c
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: Ic6da02c0039421fd5656238f5fa812574af1c268
Signed-off-by: jobol <jose.bollo@iot.bzh>
|
|
Change-Id: If2739fd2c5a19d7cd31e117e1e79c0b51451552b
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: I493c49a80ebb1fa85f586d0b0704b5682f0c3613
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: I6567b58fa0a6dd17deba4c7cccbf3b9f441730eb
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: I144bcd47b65b86dd07ca5de71514a0032166b3a6
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: Iad46596435eebdc5c521b572fd8320b52a61d197
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|