Re: [Firebird-devel] Providers, yvalve, external engines and object lifecycle

[Adriano d. S. F. <adr...@gm...>]

On 24-03-2011 12:53, Alex Peshkoff wrote:
>  On 03/24/11 18:09, Adriano dos Santos Fernandes wrote:
>> On 24-03-2011 11:59, Alex Peshkoff wrote:
>>> May be you have forgotten - one of my proposals is to not pass external
>>> handles in attach/startTransaction call. And do not pass them into
>>> engine in any way. Cause with new API we have much better way to access
>>> current context.
>>>
>> If your approach is about don't be able to use current Firebird API with
>> external attachments and transactions (initiated by client or
>> internally), I'm sorry but I can't consider it as usable.
> 
> May be you've missed in the thread 'Refcounted API objects':
> 
> We really need converter from ISC API to new interface. If in external
> engines we
> add 2 special handle values - current connection and current
> transaction, this will solve backward compatibility problem in all places.
> 
Single handle meaning different things when used in different moments
smells like fire to me.


Adriano