SOTL wrote:
> On Saturday 09 June 2007 17:56, Mark Bishop wrote:
>> Well, at least something I have always known to be true, like the sun
>> setting in the West and one daemon, one port hasn't changed. I still
>> have a warm fuzzy feeling, but I am still screwed. Thanks :)
> Don't know anything about this but I do have a question.
>
> Why can you not have one application listen on one port and then have that
> application send all the input to two other ports one in which you have one
> application listen and the other for another application? For that matter why
> could you not do this with 2, 3, 4 ports?
I guess the main hurdle is to differentiate between application data.
The daemon would listen for incoming connections. Then it would have to
look into the data payload to then route to a secondary app.
How could you code every possible data fingerprint for trafficking
between secondary apps? You would basically be writing a daemon the the
specific apps that you are doing traffic cop duty.
Forget about it if you use any kind of transport layer encryption.
/I am a network engineer and not a programmer so take my statements with
a grain of salt. :)
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:08:32 EDT