I am opening a new connection for each query. When happens is that
when the connection is closed it never returns. The ADO Close code
seems to wait in a message loop on the async thread ending -- it never
does so I get a block in the stack and routines run on top of it. If
the async thread is termi
> Do you use a different ADO connection for every query (my app does)?
There is one connection per table, but it's opened to the server once
and left open, unless there are SQL errors when it's reopened. This is
not a web application.
In my experience, ADO connections can remain open for sev
Hi Angus
Do you use a different ADO connection for every query (my app does)?
On Mon, 28 Aug 2006 14:12 +0100 (BST), you wrote:
> > There is a (very) subtle bug in ADO
> > that means ADO async threads sometimes hang when they are released.
> > This happens about one time in 100,000 calls (by
lalin wrote:
> Hello,
> I use SMTPClient for sending a email since a server with default
> smtp server of IIS. The example program find this smtp server. But in
> my program, with this code: Smtp1.Host := smtpserver; Smtp1.port
> := 'smpt'; Smtp1.FromName := name;
> Smtp1.HdrFrom := ma
> There is a (very) subtle bug in ADO
> that means ADO async threads sometimes hang when they are released.
> This happens about one time in 100,000 calls (by hang I mean they do
> not return -- the app still runs as they are in a message loop).
I'm currently testing a new application that is w
Hello,
I use SMTPClient for sending a email since a server with default smtp
server of IIS. The example program find this smtp server. But in my program,
with this code:
Smtp1.Host := smtpserver;
Smtp1.port := 'smpt';
Smtp1.FromName := name;
Smtp1.HdrFrom := mail1;
Smtp1.HdrTo:
Robert Chafer wrote:
> Hi
>
> When I use TWSocket based components and they do an async operation,
> does the operation actually happen on a separate thread and then the
> results get sent via a message to the calling thread?
ICS components do not create threads. The components and events are
exe
Hi
When I use TWSocket based components and they do an async operation,
does the operation actually happen on a separate thread and then the
results get sent via a message to the calling thread?
My reasons for asking is that is how ADO works, if you perform an
asynchronous execute, it is done on
