> Hello Group,
>
> I am looking at building an n-tier system, using Embedded FB as a
> local data storage at each tier until it gets to the "real" database
> (FB as well).
>
> Each tier needs to accept multiple, simultaneous TCP connections,
> update its local data as it comes in, then pass it upstream to the
> next tier.
>
> I know that you can not have two processes accessing the same embedded
> database, but can different threads belonging to the same process
> connect to a single database using one connection per thread?
>
> Primarily I do not want to have to deal with the threadsafe nightmare
> of maintaining my own text file based local cache at each tier. I also
> would like to make use record based locking rather than effectively
> table based locking, and also atomic operations which are impossible
> to implement using the file based records.
>
> Can it be used this way?
>
> Adam

one last comment - the only caveat as far as this is concerned is that using
the embedded server runs a risk that a badly running application which has
the server loaded into it's own memory space has the slight possibility of
trashing server memory. So be very confident of your application behaviour
with this setup. I am currently rolling out an application which uses
embedded to 3000 users. I am watching carefully for any situations where
corruption might be evident.
Alan