Merge branch 'tizen_2.2' of ssh://review.tizendev.org:29418/framework/appfw/com-core... accepted/tizen/20131022.083606 accepted/tizen/20131022.163214 submit/tizen/20131022.035758 submit/tizen/20131022.035853
authorSung-jae Park <nicesj.park@samsung.com>
Tue, 22 Oct 2013 02:26:32 +0000 (11:26 +0900)
committerSung-jae Park <nicesj.park@samsung.com>
Tue, 22 Oct 2013 02:26:32 +0000 (11:26 +0900)
commit18df4700e2dfd8410e71e47576d0e9d48b95a629
tree4c54953b2d47892f4f69a6d2c3c5671b42821ca1
parent49fb1bd2a4a2078f5f8536c391f38dd61508f15f
parent4a48be6de07cddd4ac593581c3e8cb41c187a100
Merge branch 'tizen_2.2' of ssh://review.tizendev.org:29418/framework/appfw/com-core into work

Applying socket activation should be supported by new API or Schema.
The latest com-core supports the inet & ipc socket communication using schema.
To open/connect a socket, user can select inet or ipc using schema.

remote://IPADDR:port
local://SOCKET_FILE_PATH

practical example

remote://192.168.0.1:1234
local:///tmp/.my.socket

So I just discards the systemd socket activation code now.

I think, it should be supported by new socket URI.
such as

systemd://SOCKET_FILE

This new schema should be added to handle the socket activation mode.

Conflicts:
src/secure_socket.c

Change-Id: Ib2c0d1c7f2d6b0337cd408cba11164626ca87ff4
CMakeLists.txt
packaging/libcom-core.spec
src/com-core_packet-router.c
src/com-core_thread.c