Nando Dessena wrote:

> Hello,
>
> T> Having two applications using embedded to access a single database, is a
> T> case of using the wrong tool for the job. In that case, a full server
> T> should be installed, and all applications should use the regular client,
> T> which is what it's designed for.
>
> this is a perfectly respectable opinion, but it doesn't add any useful
> element to the discussion. You basically say it should be done that
> way because it should be done that way. I think there are several
> other ways to do that, one of them would be a server embedded in a
> separate application; another way is the classic shared model. In both
> cases the advantages are a much lighter setup infrastructure and much
> higher speed for embedded access.
>

It's kind of like a carpenter who has only a screwdriver, he uses it to
drive screws, hammer nails, as a chisel to cut wood, and the results
look kind of crappy. Using embedded to do everything, to save a server
install, when a server install is the right tool for the job is the same
thing.

W