Communicate between the binders on different ECUs

Closed for Icefish RC4

except that there is no discovery or automated connection, the stuff is on.

I pushed the changes in review for integration to master.

I'll be happy to help more if you point me the code you use.

Thank you for your response.

Firstly, I must explain the use-case of Window Manager server/client on multi ECUs/displays.
The server and client ECUs have the displays each other.
And there is Window Manager server on server ECU and there is Window Manager client on client ECU.
Window Manager is necessary on each ECUs
because it controls ivi-surface in cooperation with weston
and activates/deactivates window for the applications.
Window Manager server works as service for the applications on server ECU
and for the Window Manager client on client ECU.
And Window Manager client works service for the applications on client ECU,
and uses the service of Window Manager server to show the applications such as TBT application
on client ECU to the server side display.

1)
Thank you very much!
I could resolve this issue by using sandbox/jobol/tcp.

2)
I have not try socket activation unit yet.
At the moment, I powered on the server side ECU at first,
and after the starting of AGL and Window Manager server have finished on the server side,
I powered on the client side ECU.
Then the client failed connection.

3)
If Window Manager server/client has different API,
the applications on server/client ECUs have to use different API.
Therefore if possible I want to set same binding API name to Window Manager server/client.

Thank you for your feedback.

1) Adding "After=network.target" is a good thing. I added it after rebasing the branch sandbox/jobol/tcp.

2) my understanding is that the client service start to quickly. The framework should provide on the server side a socket activation unit that will be made available by systemd. Not sure that it works. If you have time to test it.

3) I don't really understand. My current understanding is that you try in the client to export the same API that the one that you imported, like a proxy. If this is the case, you should try to declare the importation using an other api name. It should work because the name that you give on client side is unrelated to the name that you export on server side.

I maybe misunderstand what you discovered during your experiments. I really want to help and use your experiment and feedback.