Hello Patrick,
No using TSyncPop3Cli is discouraged.
I cannot check at moment. But the component has a data socket, FSocket
probably or similar. You can use the messageloop from this one if you
sete on this TWSocket MultiThread to true.
---
Rgds, Wilfried [TeamICS]
Patrick Wong wrote:
Thank you for your response.
Or use the messageLoop of TWSocket if you dont need to receive custom
messages. Set Multithreaded to true.
But may I know how? I am not quite familiar with Delphi.
Writing/using message loops is not specific to Delphi but to Windows
Hello,
I UDP sendto a request datagram to the server,
when OnDataAvailable triggers I call ReceiveFrom()
in order to read the response.
But I think OnDataAvailable is being triggered when
any datagram addressed to that port arrives, even
datagrams not sent by the destination server. How
to handle
On Aug 17, 2006, at 03:29, Arno Garrels wrote:
There's no difference between running the component in main thread
or in a worker thread given you process messages by some kind of
message loop.
Delphi's class TThread does not implement such a message loop by
default .
Think asynchrone,
and unexpected sender? Should I consider a pending
request as failed or should I just ignore such packets?
Use ReceiveFrom to know from where the packet is comming and throw it away
if you don't like the sender.
Also, if I do not use some kind of a wait function
in order to make a request
Francois Piette wrote:
Also, if I do not use some kind of a wait function
in order to make a request blocking (like WaitUntilReady),
it's mandatory to use a timer, correct?
Sorry, I don't understand.
Indeed badly expressed, I had the STUN proto in mind when I
wrote it.
In STUN, reliability
Francois Piette wrote:
I do not know how to write this as an async component method w/o
a timer, but I can write it as a sync method by some wait
function which processes messages and either starts retransmissions
or triggers a final timeout when no response hasbeen received.
There is no
Hello, I'm using ftp server im my project... but in my code I create two
sockets... with winsock2.h, and I perceive what ftpServer stops to work..
When I call before to create the sockets it listen but when I connect he it
sends me Connected but don't work...
When I call after create the
What's annoying is that a TTimer creates a window and also requires
ExtCtrls.pas to be included.
You may use Windows API to avoid TTimer and ExtCtrls.
Can you please explain why that's a problem.
In a thread, when MsgWaitForMultipleObjects returns due to pending
message(s) I use
You probably are using blocking socket. This is bad since the message pump
doesn't work anymore so ICS component can't have his events processed.
You'd better use TWSocket instead of the API.
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: Guilherme Pereira de
Hello Arno,
What's annoying is that a TTimer creates a window and also requires
ExtCtrls.pas to be included.
On my site you find a serial comport component (TCiaComPort). It has a
custom Timer on board that does not create a window, but can use an
existing window. It does not have to include
Thanks man
;-)
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Wilfried Mestdagh wrote:
Hello Arno,
What's annoying is that a TTimer creates a window and also requires
ExtCtrls.pas to be included.
On my site you find a serial comport component (TCiaComPort). It has a
custom Timer on board that does not create a window, but can use an
existing
What's annoying is that a TTimer creates a window and also requires
ExtCtrls.pas to be included.
On my site you find a serial comport component (TCiaComPort). It has a
custom Timer on board that does not create a window, but can use an
existing window.
Thanks Wilfried, but that doesn't
Francois PIETTE wrote:
What's annoying is that a TTimer creates a window and also requires
ExtCtrls.pas to be included.
On my site you find a serial comport component (TCiaComPort). It
has a custom Timer on board that does not create a window, but can
use an existing window.
Thanks
I know UDP is unreliable and packets may be lost, but are they
checksum'd again corruption? And if the checksum fails, is the packet
then lost?
The real question is whether my UDP protocol needs to add it's own
checksum.
Also, how reliable is having multiple applications listening for the
Angus Robertson - Magenta Systems Ltd wrote:
I know UDP is unreliable and packets may be lost, but are they
checksum'd again corruption? And if the checksum fails, is the packet
then lost?
I guess it is lost, since I guess that checksum checks are done on the
IP layer.
The real question
Hello Arno,
I have to check, but I think there is also be an option to create a
timer without have a window. then it post a message to a message
queue.
another option is to create a custom timer using a thread.
---
Rgds, Wilfried [TeamICS]
Unfortunately the callback requires a window handle as well.
And what is the problem ? Use the TWSocket handle.
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Thursday, August 17,
This is less of a socket question and more of an implementation question.
Imagine a server with many concurrent connections but that only allows one
connection at a time to submit a request, access/manipulate data and then
send the results back to all other connections. In other words all
Unfortunately the callback requires a window handle as well.
But zero is fine for the handle. I use this code in a DLL to close
a database on inactivity.
Angus
procedure TimerProc (Wnd: HWnd; Msg: Integer; Id: Integer;
Hi
I have just downloaded ICS version 5 and am trying to install this into Delphi
2. I have followed the instructions in the readme file but get an error during
the install in relation to the icslogger component saying cannot assign to a
read-only property for the line
FLogFile.Size := 0;
22 matches
Mail list logo
