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" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Thursday, March 08, 2007 8:18 PM
Subject: Re: [twsocket] TWSocket not connecting for me
> 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 the help.
>
> regards,
>
> Andy
> Fastream Technologies wrote:
>> 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.
>> If you want parallel execution in the same thread, use async/events plus
>> GetMessage of your own.
>>
>> Best Regards,
>>
>> SubZero
>>
>> ----- Original Message -----
>> From: "info2004" <[EMAIL PROTECTED]>
>> To: "ICS support mailing" <twsocket@elists.org>
>> Sent: Thursday, March 08, 2007 7:37 PM
>> Subject: Re: [twsocket] TWSocket not connecting for me
>>
>>
>>> 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" <twsocket@elists.org>
>>>> Sent: Thursday, March 08, 2007 6:46 PM
>>>> Subject: [twsocket] TWSocket not connecting for me
>>>>
>>>>
>>>>> 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 created the TWSocket, then I
>>>>> run
>>>>> through a state machine to query the database, make the connection
>>>>> etc.
>>>>>
>>>>> Does anyone know why .State would stay at wsConnecting?
>>>>>
>>>>> I can connect to the server manually using telnet, and I don't have
>>>>> any
>>>>> problems providing additional info. Just didn't want to overload the
>>>>> email at this point.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Andy
>>>>> --
>>>>> 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
>>> --
>>> 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
>>
>
> --
> 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
--
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
