ecore_con/ecore_ipc: flush should wait for connection.
authorGustavo Sverzut Barbieri <barbieri@profusion.mobi>
Mon, 19 Dec 2016 14:57:09 +0000 (12:57 -0200)
committerGustavo Sverzut Barbieri <barbieri@profusion.mobi>
Mon, 19 Dec 2016 15:03:33 +0000 (13:03 -0200)
commita7657e821f81eab59a719c81d3994194492476a6
tree7e0a48ab43b60925301e5f7f86c75b6030e6c689
parentfe668ef52c74f52c45d1c0af6a1df791ab412e35
ecore_con/ecore_ipc: flush should wait for connection.

Some applications will create the handle, immediately send data, flush
and delete it, expecting the data to be sent to remote peer.

This is a bad behavior as the application would become unresponsive
until the connection is established, data can be written (since
depends on server consuming it), then allow it to be closed.

A proper behavior here would be to chain based on events, with the
usage of a copier would be simply wait for "done" event.

However the legacy API allowed this and terminology depends on this
awkward "feature", thus be bug-compatible.

This fixes T5015.
src/lib/ecore_con/ecore_con_legacy.c
src/lib/ecore_ipc/ecore_ipc.c