Hi,
I'm a bit confused here. As an experience here for the UTEthernity there
were some problems with packet losts over the network (usually when used
over a none private networks) rather than problems with socket buffer
overflows. I thought the whole problem is with network commiunication
problems rather than too many unhandled messages on a socket.
So, even with that still the TCP-UDP bridge would work. If a single demon
does all the brigings then it knows the ammount of data sent on the UDP
sockets. As the OS socket buffers is known (and can be set), the demon can
(virtually) drop the messages if they exceed the limit and send a faliure
message back to the sender. It wouldn't let the OS drop the packets.
The demon does not seem to be a huge work. In fact I think it only need a
few hours to design and maybe just a few more hours to implement.
(probably not by me ;) although I could do the simple bridging on my pc)
I do think that this is not at all a good thing to do perminantly. Rather
it can be used to fasten the development process. It can be used
temprorily to move everything to TCP, and then work on each module one by
one.
--Millenarian
> Hi!
>
> I don't think that's a good ideia, because the main problem won't be
> solved: even with local communications, the UDP packets may be lost. If
> one the the system UDP buffers gets full, the OS kernel will start to
> drop packets.
>
> So, I guess it would be a lot of pointless work... it's better to
> spend a little more time doing the thing right, that spend more time
> (the proxy + the TCP layer) with no reason.
>
> Yours
>
> Miguel Arroz
>
> On 1 de set de 2004, at 1:15, Mahdi Milani Fard wrote:
>
>> Hi,
>>
>> I've got a suggestion which might help to fasten the development of
>> the TCP communication systems. We can use a demon as a TCP to UDP
>> bridge for
>> each piece of the system. The demon would listen to one or more TCP
>> port
>> and then send the received data as local UDP on the same machine. It
>> will
>> also read from local UDP and pass it over the network using TCP. There
>> will be no need to change the any modules, as they can simply use
>> local UDP ports. This way, the demon could send a new type of message
>> (a so called KA maybe) to sender if there is a problem in sending the
>> data over
>> the network (although this should be used with very small ttl.)
>> However, I
>> think it needs a bit more thought and it might not be practical at
>> all.
>>
>> This seems to be a patch rather than a real solution, but at least it
>> can
>> be used temporarily with some modules while working on the others. We
>> can
>> start with the patch and then little by little remove it for each
>> module.
>>
>> --
>> Mahdi Milani Fard
>> Member of UTEternity
>> Tehran, Iran
>>
>>
>>
>>
>
> "I felt like putting a bullet between
> the eyes of every Panda that wouldn't
> scr*w to save its species." -- Fight Club
>
> Miguel Arroz - arroz@guiamac.com - http://www.guiamac.com
This archive was generated by hypermail 2.1.3 : Wed 01 Sep 2004 - 18:43:20 GMT