From: Vincent T. <vt...@un...> - 2011-02-11 18:00:43
|
On Fri, 11 Feb 2011, Michael Taubert wrote: > > Am 11.02.2011 um 13:23 schrieb Carsten Haitzler (The Rasterman): > >> On Fri, 11 Feb 2011 07:50:46 +0100 Michael Taubert <mi...@ar...> >> said: >> >>> Good morning everyone, >>> >>> how do I identify the port a client has been connected to? >>> >>> I've got a server that is opening two ports for different purposes. When a >> >> on the server side you will create 2 Ecore_Con_Server objects - each listens ON >> a specific port that you set it up to listen on. when the client joins u get >> the client handle. FROM the client handle u can get the server handle. this >> tells you which server (And thus which port) it connected to. >> > Thanks a lot. Didn't got to that. > Never thought of identifying it by the server handle. Instead I was digging through Ecore_Con_private.h. Hehe.. when it's private, it's not public :) So it's not the correct place to look at such info Vincent > >>> client connects, I could not figure out how to identify the port, in the >>> Ecore_Con_Client_Add-callback. Fortunately, the server listens on a public IP >>> and on localhost, so I thought about to identify the connections through the >>> ip address. But anyone got a more precise approach for this? >>> >>> Thanks, >>> Michael >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>> Pinpoint memory and threading errors before they happen. >>> Find and fix more than 250 security defects in the development cycle. >>> Locate bottlenecks in serial and parallel code that limit performance. >>> http://p.sf.net/sfu/intel-dev2devfeb >>> _______________________________________________ >>> enlightenment-devel mailing list >>> enl...@li... >>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>> >> >> >> -- >> ------------- Codito, ergo sum - "I code, therefore I am" -------------- >> The Rasterman (Carsten Haitzler) ra...@ra... >> > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > |