Angus Robertson - Magenta Systems Ltd wrote:
> ADO also supports non-blocking SQL Server commands, with an event
> triggered when the command finishes, so you don't even need threads
> for SQL. ADO uses a thread internally, but that's a Microsoft
> problem, not ours.
Also non-blocking sockets are
Arno,
Arno Garrels wrote:
> info2004 wrote:
>> Hi,
>>
>> I am using V6 beta with Turbo Delphi 2006.
>>
>> Can someone tell me which threaded server demo I should use as my
>> base for an app please.
>
> AFAIK none of the multi-threading demos is converted to V6 yet.
> ThrdSrv uses a design "one th
> Instead put blocking, lengthy tasks like executing a SQL
> into worker threads and send the result when thread has finished
> the job.
ADO also supports non-blocking SQL Server commands, with an event
triggered when the command finishes, so you don't even need threads for
SQL. ADO uses a threa
info2004 wrote:
> Hi,
>
> I am using V6 beta with Turbo Delphi 2006.
>
> Can someone tell me which threaded server demo I should use as my
> base for an app please.
It depends on your application. Most applications do not require
any multi-threading for the socket I/O. Since ICS uses non-blockin
Hi,
I am using V6 beta with Turbo Delphi 2006.
Can someone tell me which threaded server demo I should use as my base for an
app please.
MtSrv points you to ThrdSrv. ThrdSrv has ThrdSrv, V2 and V3.
V2 works but does not like WM_TRIGGER_EXCEPTION.
V3 complains at TWSocketThrdServer - not foun
