>> btw: You frequently don't need thread with ICS because it is asynchronous
>> and non-blocking. It multitask automatically WITHOUT using threads.
>> Programming is then much easier...
> To date, I have used the components without additional threads. This is
> my first experience using threads. I
I do not think TWSocketServer is thread-safe! Am I wrong?
Regards,
SZ
- Original Message -
From: "info2004" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Thursday, March 08, 2007 9:45 PM
Subject: Re: [twsocket] TWSocket not connecting for me
> Francois,
> Francois PIETTE wrote
Francois,
Francois PIETTE wrote:
> I had not noticed you where using threads. SZ is right: you need a message
> pump in your thread.
> There are several multithread sample delivered with ICS-V5 (They are good
> for ICS-V6)
>
> btw: You frequently don't need thread with ICS because it is asynchro
I had not noticed you where using threads. SZ is right: you need a message
pump in your thread.
There are several multithread sample delivered with ICS-V5 (They are good
for ICS-V6)
btw: You frequently don't need thread with ICS because it is asynchronous
and non-blocking. It multitask automati
It's not that complex at all. So even if you have like,
while(!Terminated)
TWSocket.ProcessMessages();
it should be ok for simple use. There are some more complex use of
GetMessage but not needed for single twsocket/thread.
Best Regards,
SZ
- Original Message -
From: "info2004" <
SZ,
I had a look through the list and saw the ref's to get and peek etc.
I did a grep on the source and decided to use TWSocket.ProcessMessages
in my Thread.Execute loop.
This seemed to work. The socket connects and I send my data.Are there
going to be any pitfalls in doing this?
Thanks for t
Francois,
Thanks for the response.
The .State parameter stays at wsConnecting for minutes - then I terminate.
I am going to look at SZ's messagepump angle, as that sounds quite
promising.
Regards,
Andy
Francois PIETTE wrote:
> Maybe your problem is that when calling Connect you ask the compo
Search for MessagePump/GetMessage API function in this list's archieve to
learn more. The TWSocket also contains a messagepump() function to see. If
you use sync methods, then the message pump is implicitly called until
needed. The bad thing is that there is a single action done in the thread.
Hello:
Most ISP's SMTP servers limit the amount of
concurrent connections from the same source to about
10 or 20. This is intended to prevent automatic
spamming and mail bombing runs, or to at least hinder
or limit their impact. This is pretty much an
industry standard nowadays (along with rej
> Are there providers which limit the number of concurrent SMTP
> connections? In other words: Do I have to make the maximum number
> of connections for asynchronous operation flexible and what would
> be a good practice approach (besides making it user configurable).
There is no limit imposed by
Maybe your problem is that when calling Connect you ask the component to
connect. You get control back immediately (asynchronous method) while the
component try to establish the connection for you. Once the connection is
established, you have OnSessionConnected event which is triggered. This is
SZ,
Erm, I guess not. What do I need for that or where do I go to find out?
Regards,
Andy
Fastream Technologies wrote:
> Do you have a message pump in the thread.execute?
>
> Regards,
>
> SZ
>
> - Original Message -
> From: "info2004" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
Veit Zimmermann wrote:
> Hi
>
> Are there providers which limit the number of concurrent SMTP
> connections?
Most likely.
> In other words: Do I have to make the maximum number
> of connections for asynchronous operation flexible and what would
> be a good practice approach (besides making it u
Do you have a message pump in the thread.execute?
Regards,
SZ
- Original Message -
From: "info2004" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Thursday, March 08, 2007 6:46 PM
Subject: [twsocket] TWSocket not connecting for me
> Hi,
>
> I have a problem with TWSocket.State
Hi,
I have a problem with TWSocket.State staying as wsConnecting after I try
and connect.
I am using a thread to execute an SQL query. For each result from this
query, I connect to a remote server using the TWSocket, and send some
data. That's the plan.
In the Thread.Execute procedure, I have
Hi
Are there providers which limit the number of concurrent SMTP
connections? In other words: Do I have to make the maximum number
of connections for asynchronous operation flexible and what would
be a good practice approach (besides making it user configurable).
TIA
Veit
--
To unsubscri
16 matches
Mail list logo
