"Jim Starkey" <jas@...> wrote:

>
> Good point. It doesn't. Time to get creative again. How about an
> attachment specific generic interrupt token that kill anything that
> happens to be running?

You will be laughing, but I was going to suggest exactly this ;-)

1) It doesn't require multiple tokens/locks at all
2) It does what users want, interrupting the blocked API call
3) An AST could be added to the already existing att_id_lock that could
handle this task
4) The internal infrastructure is in place for about 5 years (it terminates
an attachment after its endpoint dies in SS builds)

All user need is to retrieve the attachment_id via isc_database_info() and
pass it to the engine which then signals the lock.

P.S. Time to come back to the API proposals?


Dmitry