At 02:00 AM 12/13/2004, Nando Dessena wrote:

>I take it that the structure of a client application would be:
>
>EmbeddingApp.exe loads-> firebird.dll loads-> someProvider.dll

Right. And EmbeddingApp can make as many connections to the
database as it requires and they will run against each other
using fine-granularity multi-threading.

If you enable database sharing, then other processes can also
attach to the same database, either locally or through the
server program. Access is coordinated through the lock table.

>All in the same process space, right?

Right. There's no reason that a two process variant could not
be created where the client links to a stub and uses some variant
of interprocess communication to talk to a different server
application without going through TCP.

>A> To emulate SuperServer, Vulcan provides a single, thin, server program
>A> that accepts remote connections and provides database services.
>
>Any new thoughts about publicly documenting the network protocol so
>that the this server program can be emulated?

Yes. One such though is that Carlos Guzmán Álvarez is believed to have
the start of such a document. Another is that NETProvider has a reasonably
good, clean implementation that can be used as documentation. A third
is that the protocol is antiquated and not at all appropriate for local
communication.


Regards,


Ann