Bluebugs / freebox-elixir

Automatically exported from code.google.com/p/freebox-elixir
0 stars 0 forks source link

No way to know the reason of a TCP socket connexion failure. #11

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Using the TCP client socket of the Elixir API (thru
ecore_con_server_connect, ...), and as far as I searched, I found no way to
get more information when a connexion fails.

Especially I cannot know if it is because:
- hostname resolution failure.
- IP not responding
- remote server explicitely refused the connexion.
- ...

Original issue reported on code.google.com by alexandr...@gmail.com on 3 May 2010 at 11:34

GoogleCodeExporter commented 9 years ago
Yes, there is actually no way to know what goes wrong in Ecore_Con module. This 
need to 
be patched upstream. An upstream bug should be opened ( 
http://trac.enlightenment.org/e/newticket ), or better a patch could be 
provided ( 
http://trac.enlightenment.org/e/browser/trunk/ecore/src/lib/ecore_con ). When 
the 
upstream project has been fixed, we will just need to update Elixir bindings.

Original comment by moa.blue...@gmail.com on 3 May 2010 at 12:23