Re: [Firebird-devel] Embedded superserver

[Jim S. <ja...@ne...>]

Leyne, Sean wrote:

>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, there really isn't a contradiction.  The entire system is 
architected around the idea that the remote interface/server combination 
is a transparent piece of plumbing.  There should be no theoretical or 
practical problems with an application performing direction database 
access fire off some threads to let other folks talk to the database 
running in his process other than the obvious one that database access 
isn't available when the application program isn't accessible.

There is a problem (if I remember correctly) in Firebird up to and 
including head that the embedded build doesn't perform user 
authentication.  This may provide the motivation to straighten out some 
conditionals in jrd.cpp, but it doesn't affect the plumbing.

It's just code, folks.

-- 

Jim Starkey
Netfrastructure, Inc.
978 526-1376