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

[Alex P. <pes...@ma...>]

> In my new version of why.cpp things like CAttachment (C*) classes gone
> in favor of YAttachment (Y*) objects. Things are much simple and
> effective, became directly usable without legacy handles, may use the
> same API (semantics defined in yvalve) for client and external code
> running on the server.
>

Adriano, sorry - it's too late here now and I can't give complete full
answer right now. If your modifications:
1. Do not take new special measures (like IYvalveManagement interface)
to coordinate between engine and yvalve.
2. Do not break reference counters functionality.
I see no problems with them. If not - please delay them till the end of
discussion.