--- In Firebird-Architect@yahoogroups.com, "Aleksey Karyakin"
<karyakin@c...> wrote:

>
> The diagnostic object is implemented by the underlying API level.
> This is a pure C API, completely portable, doesn't rely on

exception

> handling or thread-local data and is object-oriented.

In reality, there's a conceptual problem. The proposed diagnostic API
is local-oriented. Literally mapping it to remote objects and calls
would result in keeping the diagnosic object on the server. However,
it's inacceptable for client-server performance, where diagnostic
object should be always local, implemented by the client proxy, and
received by value from server along with response packet.

This actually means API/remote protocol split, which is fine for me
but anyone who believe in location transparency and uniform layering
would disagree :)

> Regards,
> Aleksey Karyakin