Nando Dessena wrote:

> "W",
>
> T> It's kind of like a carpenter who has only a screwdriver, he uses it to
> T> drive screws, hammer nails, as a chisel to cut wood, and the results
> T> look kind of crappy. Using embedded to do everything, to save a server
> T> install, when a server install is the right tool for the job is the same
> T> thing.
>
> restating the concept is not going to make it any more valid. ;-) I
> assure you I got it the first time, and I think I have explained why I
> can see room for improvement.

You didn't really explain what you were trying to do, having taken some
time to think about it, this is probably close:

You have a shared library (.so in Unix/Linux, DLL in Windows) that
contains the Firebird engine, then you build wrapper
applications/libraries around it, so for example superserver would be a
wrapper application that calls the Firebird Engine, Classic would be a
different wrapper application that calls the same Firebird Engine, and
embedded would be a wrapper library that calls the engine directly. The
client would call either the superserver or classic wrapper application.

This sounds a lot like Vulcan.

W