Subject Re: [Firebird-Architect] External Engines Implementation Details
Author Alex Peshkov
On Thursday 27 December 2007 19:17, Jim Starkey wrote:
> Adriano dos Santos Fernandes wrote:
> > I also need to communicate y-valve handles to engine, as Vlad does in
> > exec. stmt branch. But the solution Vlad is using doesn't work with
> > CONNECT and TRANSACTION START triggers, as he said.

What do you mean here? There is no new conection and no new transaction. How
are triggers related with it?

> > I think these handles could be communicated to the engine via internals
> > DPB/TPB. BTW, isn't the isc_dpb_trusted_role an internal DPB? Should not
> > we create a generic mechanism for internal DPB/TPB?

Generic mechanism is too loud word for very simple thing - removing a set of
tags from parameters block in remote listener. As soon as we start to talk
about embedded access word 'internal' looses any sense.

> > And yes Virginia :-), this is one more thing that violates y-valve
> > layering, but it's how Firebird current works.
> Let me say that you are making a very serious mistake that Firebird
> developers will regret for years to come and leave it at that.

I'm completely agreed with Jim here.
Instead of thinking how to violate providers architecture may be it's better
to discuss how to implement new features, not breaking it?