WM Variables on the stack does not consume time. Only if something has to
WM be initialized or so, like for example a long string.
I am not sure that is consume no time. If I remember well, local vars
are dynamicaly allocated and deallocated each time you go into the
procedure, so it
Hello Francois,
So I was wrong and it is nice because I tended to avoid local vars
declarations :-) But I remember having read somewhere that
using/accessing local vars was slower than global ones and this why I
said that.
WM Variables on the stack does not consume time. Only
So I was wrong and it is nice because I tended to avoid local vars
declarations :-) But I remember having read somewhere that
using/accessing local vars was slower than global ones and this why I
said that.
The quality of a program is somewhat in inverse ratio to the number
- Original Message -
From: Wilfried Mestdagh [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Saturday, August 20, 2005 8:39 AM
Subject: Re: [twsocket] Transfer with UDP
Hello Dan,
Buffer : array [0..5] of char;
Variables on the stack does not consume
Hi Guillaume,
I am using Tsocket UDP because I need transfer high speed data, but is more
complicated because the sent machine send 720 strings in 4 seconds, and a
string maybe contained large data.
The most important in the application is the time, then receive data and
process it must be
I am using Tsocket UDP because I need transfer high speed data, but is more
complicated because the sent machine send 720 strings in 4 seconds, and a
string maybe contained large data.
The most important in the application is the time, then receive data and
process it must be fastest.
Don't
Hello Juan,
This can explain wy you loose data. UDP is fast but not realble. If you
dont want to loose data then you have to use TCP.
---
Rgds, Wilfried
http://www.mestdagh.biz
Friday, August 19, 2005, 16:11, Juan Pablo Franco wrote:
Hi Guillaume,
I am using Tsocket UDP because I need
Again,
If I use TCP, the time is over. I need transfer important data in little time.
SENT MACHINE
overlaySocket.SendStr(Msg);
RECEIVE MACHINE:
procedure TFVisor.overlayListenDataAvailable(Sender: TObject; ErrCode: Word);
var
Buffer : array [0..5] of char;
Src: TSockAddrIn;
Juan Pablo Franco a écrit :
Again,
If I use TCP, the time is over. I need transfer important data in little time.
i'm not quite sure TCP has such overhead compared to UDP that your time
window should be over while sending, IMHO.
if you're on a LAN, and that your data processing doesn't
IS PROBABLY THAT BUFFER COLAPSE
What do you mean ?
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: Juan Pablo Franco [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Friday, August 19, 2005 6:16 PM
Subject: Re: [twsocket] Transfer with UDP
Hello Juan,
If I use TCP, the time is over. I need transfer important data in little time.
Ok. If it is not importand to loose data (you can ask server to transfer
it later) because real time is more importand then you have to use UDP,
but if speed is importand then read on.
For the packets
- Original Message -
From: Juan Pablo Franco [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Friday, August 19, 2005 5:16 PM
Subject: Re: [twsocket] Transfer with UDP
RECEIVE MACHINE:
procedure TFVisor.overlayListenDataAvailable(Sender: TObject; ErrCode:
Word
Hello Juan,
If I use TCP, the time is over. I need transfer important data in little time.
As Guillaume and others already stated:
the main problem with UDP is that you know you have sent, but you never
know *what* has been received - unless you have established a heavy
protocol which
13 matches
Mail list logo
