RE: [Firebird-devel] Embedded superserver

[Leyne, S. <Se...@br...>]

Roman and Nando,

> > c) the same server process that serves database connections needs to
> > provide other services to remote clients, using different ports and
> > protocols, including but not limited to SOAP and HTTP. For those who
> > are concerned about the scalability of my all-in-one solution, don't
> > worry: The workload is never going to be heavy.
>=20
> It was not intended to be your case :) Since Sean is not buying c), I
> created a case, pretty legal one, when Jim's solution is the only
possible
> one. Maybe he buys this one :)

Nope.

Just to be clear, what I don't "buy" is the need expressed.

Ironically, my BroadView application and Nando's are very similar.  It
provides an extensive set of functions and services to applications (via
DCOM, SOAP...).  We also provide selected remote applications direct
database access.

Accordingly, our application is equally dependant on the FB
service/server.

But the functionality that Nando is suggesting seems to run counter to
the appropriate "layering" of the solution.

If you want to embed the database into your application than you wrap
the application around the engine -- fine.  This means that no outside
access is provides to your 'closed' environment or you must expose your
own server functions to expose/manage the database access.

He wants to completely surround the engine but still provide external
'native' access to the engine.  This appears to be a contradiction.


Sean