But I'm talking about fbclient.dll.
It is problematic, because in that concept mean, one times when you give
a call back address.
fbclient can call any time during application run independently to
isc_cancel_event.
I did see any problem with second channel. In normal model when I
canceling some async operation,
I in critical section invalidate call backs, wait for thread finish and
that's all.
From my point of view, I use fbclient wrong way or there is bug in
fbclient.
Slavek
Ing. Slavomir Skopalik
Executive Head
Elekt Labs s.r.o.
Collection and evaluation of data from machines and laboratories
by means of system MASA (http://www.elektlabs.cz/m2demo)
-----------------------------------------------------------------
Address:
Elekt Labs s.r.o.
Chaloupky 158
783 72 Velky Tynec
Czech Republic
---------------------------------------------------------------
Mobile: +420 724 207 851
icq:199 118 333
skype:skopaliks
e-mail:skopa...@elektlabs.cz
http://www.elektlabs.cz
On 25.8.2017 12:42, Jiří Činčura wrote:
I supposed that after that call, no call back happen, but in reality it
is happen.
Is it correct?
I'd say it is (I have the same in FirebirdClient during tests under
load) and even understandable. Given by design it's 2nd "channel" and
the processing between regular connection and aux connection is not
synchronous. Well, at least on such assumption I've built it in
FirebirdClient.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
