🚀 go-pugleaf

What is a good UDP component ? I've been using TClientSocket and 
TServerSocket for TCP.

-- 
Jonathan

"Jonathan Benedicto" <incorrect@no.server> wrote in message 
news:41f826bd@newsgroups.borland.com...
> In the current implementation of my app, the data is received in 
> compressed 612 byte packets, and then a thread tkaes it and splits it into 
> 100 byte packets for sending over a connection.
>
> I had thought that the splitter would help with a dial-up connection, but 
> now I think that I should take it out.
>
> I really only want good quality with extremely low latency, and so I don't 
> know that I can have too many packets lost, maybe I should reduce the 
> audio sample size and use UDP.
>
> -- 
> Jonathan
>
> "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
> news:41f81de7@newsgroups.borland.com...
>>
>> "Jonathan Benedicto" <incorrect@no.server> wrote in message
>> news:41f8176c$1@newsgroups.borland.com...
>>
>>> I'm trying to stream compressed audio between computers.
>>>
>>> Does TCP have too much latency to make be able to do
>>> it well ? Should I use UDP instead ?
>>
>> That depends on what you are trying to accomplish in the first place. 
>> Since
>> the data is being compressed, use TCP if data integrity is important, 
>> since
>> UDP can deliver data in different ordering than it was sent and also data
>> may be lost altogether.  On the other hand, if the data is being 
>> comressed
>> small enough that blocks of audio can fit into individual UDP packets
>> (usually 8K max), and you don't care if packets get lost, then UDP is 
>> fine.
>>
>>
>> Gambit
>>
>>
>>
>
>