and fyi, ecore_con_local_win32 used to work before the migration to eo. I tested it with a client/server, efreetd also was working
Vincent On Wed, Dec 7, 2016 at 6:50 AM, Vincent Torri <[email protected]> wrote: > On Wed, Dec 7, 2016 at 12:50 AM, Gustavo Sverzut Barbieri > <[email protected]> wrote: >> Hi all, >> >> It seems ECORE_CON_LOCAL_* is broken on Windows given reports on >> efreetd not working there, the code is very different from other >> protocols, see ecore_con_local_win32.c >> >> Since I will replace Ecore_Con_Server with a wrapper on top of >> Efl_Net, I'm wondering what to do... I don't have a windows machine or >> windows development environment to write a new Efl_Net set of class >> for it (if you do, please talk to me so I can get an SSH access). >> >> More than that, looking at local_win32.c I wonder how that would work, >> since unlike UNIX path, it doesn't encode the service name/port in the >> path, but the process id (I guess it's like the PID), thus one process >> won't find the other... >> >> That's to say that legacy compatibility is not an issue in that case. >> >> Then what I propose to write an Efl_Net_Local_Fallback that uses a >> local path to encode a localhost (127.0.0.1) TCP port. Then the logic >> would be: >> >> - server: bind(127.0.0.1:0), getsockname() to check the port, >> fprintf(fp, "%hu\n", ntohs(addr.sin_port))... \n is used to avoid >> partial writes (unlikely) to file. >> >> - dialer (client): fopen() + fread() + verify trailing \n, then >> connect to 127.0.0.1:$port >> >> - path is encoded like in UNIX, just "/" is replaced with "\" for >> windows. "~" is also handled like in Windows, such as User\username... >> >> Then it would provide some usable solution where a native local >> communication is not available... Of course this is fully testable on >> UNIX as well, then we don't rely on Windows to test it. >> >> Agreed? > > no. > > named pipes are used. The name of a named pipe must have the following > scheme : \\.\pipe\mypipename on local computer (or > \\servername\pipe\mypipename on a remote computer) > > you keep thinking that unix and windows are the same... ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
