"Aleksey Karyakin" <karyakin@...> wrote:

>
> Nothing has to be redesigned, really. In theory, there should appear
> new message type in remote protocol, but the existing one for
> isc_free_statement () could fit. Overall client interface change is
> indeed adding a new constant in ibase.h as Borland did.

Yes, it could work.

> Cancelling
> users' own queries is easy and can be done over a weekend.

Via the separate connection - agreed. Otherwise, you'll need to write a full
featured port level synchronization over the weekend. I suspect this is
possible in Vulcan (given the proper port encapsulation it has), but the FB2
codebase is not the best place for such experiments.

> The main problem I see is the lack of Classic (single-threaded
> server) support. Isn't Classic doomed to extinction? Anyway, Classic
> can't merely be stopped properly if it executes a query.

You mean it doesn't enter the rescheduling point and hence cannot react to
the cancellation flag?


Dmitry