aboutsummaryrefslogtreecommitdiffstats
path: root/src/Makefile_Ecore_Con.am
diff options
context:
space:
mode:
authorGustavo Sverzut Barbieri <barbieri@profusion.mobi>2016-09-15 21:43:19 -0300
committerGustavo Sverzut Barbieri <barbieri@profusion.mobi>2016-11-08 22:40:34 -0200
commit98fe627ca41f648e0dbf4e0072efa05057f273ca (patch)
treef996295c5bcdff77e30707a9379f97e031f0d13f /src/Makefile_Ecore_Con.am
parentLuncher Gadget Theme: Fix alignment just a hair to a solid middle ground betw... (diff)
downloadefl-98fe627ca41f648e0dbf4e0072efa05057f273ca.tar.gz
efl_net_session and efl_net_control for ConnMan
These are objects to allow control of networking devices (efl_net_control) as well as an application to request for connectivity (efl_net_session). They are loosely based on ConnMan.org, which we already use in Enlightenment Window Manager via DBus access with Eldbus. However they do not map 1:1 as the goal was to expose a viable subset of controls but in a simple and general way, thus nome strings were converted to enums, some arrays of strings were converted to bitwise flags, some names were made more general, such as "service" was turned into "access point" so it doesn't generate confusion with other "network services" (ie: http server), or "favorite" that was renamed to "remembered". Some behavior are slightly different (yet able to be implemented on top), such as "Service.MoveBefore" and "MoveAfter" were converted to a numeric "priority", calculated from service's list index, changing the priority will reoder the list and thus generate the MoveBefore and MoveAfter DBus commands. ConnMan was chosen not only because we already use it, but because its DBus API is sane and simple, with the server doing almost all that we need. This is visible in the efl_net_session, which is completely done in the server and do not require any extra work on our side -- aside from talking DBus and converting to Eo, which is a major work :-D NOTE: ConnMan doesn't use FreeDesktop.Org DBus interfaces such as Properties and ObjectManager, thus we cannot use eldbus_model_object. There are two examples added: - efl_net_session_example: monitors the connection available for an application and try to connect. You need a connman compiled with session_policy_local and a configuration file explained in https://github.com/aldebaran/connman/blob/master/doc/session-policy-format.txt to get a connection if nothing is connected. Otherwise it will just monitor the connectivity state. - efl_net_control_example: monitors, plays the agent and configure the network details. It can enable/disable technologies, connect to access points (services) and configure them. It's quite extensive as allows testing all of ConnMan's DBus API except P2P (Peers).
Diffstat (limited to 'src/Makefile_Ecore_Con.am')
-rw-r--r--src/Makefile_Ecore_Con.am12
1 files changed, 11 insertions, 1 deletions
diff --git a/src/Makefile_Ecore_Con.am b/src/Makefile_Ecore_Con.am
index 3e9742e6ab..6fcbcba492 100644
--- a/src/Makefile_Ecore_Con.am
+++ b/src/Makefile_Ecore_Con.am
@@ -24,6 +24,10 @@ ecore_con_eolian_files = \
lib/ecore_con/efl_net_ssl_context.eo \
lib/ecore_con/efl_net_dialer_ssl.eo \
lib/ecore_con/efl_net_server_ssl.eo \
+ lib/ecore_con/efl_net_control_access_point.eo \
+ lib/ecore_con/efl_net_control_technology.eo \
+ lib/ecore_con/efl_net_control.eo \
+ lib/ecore_con/efl_net_session.eo \
lib/ecore_con/ecore_con_eet_base.eo \
lib/ecore_con/ecore_con_eet_server_obj.eo \
lib/ecore_con/ecore_con_eet_client_obj.eo \
@@ -104,7 +108,13 @@ lib/ecore_con/efl_net_server_udp_client.c \
lib/ecore_con/efl_net_socket_ssl.c \
lib/ecore_con/efl_net_ssl_context.c \
lib/ecore_con/efl_net_dialer_ssl.c \
-lib/ecore_con/efl_net_server_ssl.c
+lib/ecore_con/efl_net_server_ssl.c \
+lib/ecore_con/efl_net-connman.h \
+lib/ecore_con/efl_net-connman.c \
+lib/ecore_con/efl_net_control_access_point-connman.c \
+lib/ecore_con/efl_net_control_technology-connman.c \
+lib/ecore_con/efl_net_control-connman.c \
+lib/ecore_con/efl_net_session-connman.c
EXTRA_DIST2 += lib/ecore_con/ecore_con_legacy.c