Subject Re: [Firebird-Architect] Services API
Author Dmitry Yemanov
"Ann W. Harrison" <aharrison@...> wrote:
> Another feature of Firebird that did not survive the transfer to Vulcan
> is the Services API. There is a general agreement that it will be
> implemented as a separate provider under the dispatch module and that
> the remote plumbing (server and remote provider) will transmit its calls.
> [snip]
> My suggestion is that we separate each of the utilities into a backend
> shared library and a front-end program that calls the library. The
> shared library uses the services API as its interface. The program is a
> very thin layer that provides a user interface for the library.

This is more or less something I've been thinking about myself. My full
support to this idea.