Re: [Firebird-devel] library soname for fbclient and fbembed

[Roman R. <rro...@ac...>]

> Well, I kind of disagree. Just because you can't serve *other* processes,
> fbembed is still serving *your process*. The communication between fbembed
> and your app is in-process but it is not any less client/server.
> 
> In other words, you're "embedding" the "server" into your process. But that
> does not *have* to mean your process becomes a server itself.

Similar discussion was done when Jim were presenting his ideas in 
FB-Architect. Finally it seems to be an agreement that we have "server" 
and we have "engine". So what you call an "inprocess" server is 
something we call "embedded engine".

So unless the core devs disagree, I'd say that we stick to "server" as 
something that can receive requests from other processes (IPC or TCP) 
and "engine" as something that can handle all database operations. Note 
that "server" includes "engine".

Roman