Subject | Re: [firebird-support] embedded twice |
---|---|
Author | Bogusław Brandys |
Post date | 2006-03-29T08:16:23Z |
Alan McDonald wrote:
Now I fully understand this issue.
I even discover that if firebird embedded would optionally create only
*one* superserver instance on the first loading into memory - it will be
a new feature ;)
All other applications will just use fbembed.dll as a client connecting
to existing embedded instance.
I'm sure this is difficult or there are obvious reasons why it can't
work that way.
I have in my mind such example: two applications - one which work on
database using GUI and one which just collect data from external device
and store in the same database.
Of course using SuperServer is a solution but someone could say that
embedded should allow such scenario also.
Regards
Boguslaw
>>> What about windows fbembed.dll ? Can it be accessed by two concurrentThank You Helen,Ann,Alan,Adam and all !
>>> programs running from the same directory ?
>> Yes, but only the first instance will get access to the database if
>> you both applications to access the same database.
>>
>>> I heard something about shared DLL's but I'm not sure if this is
>>> that case.
>> Sharing a DLL between several applications simultaneously is what DLLs
>> are all about.
>>
>> The whole Windows operating system itself is simply a large collection
>> of DLLs, which are shared by all the applications that are running.
>>
>>
>> Best Regards
>>
>> Stefan
>
> but this sort of sharing results in multiple instances of the DLL running.
> For embedded, there must be only on instance for you to increase the number
> of users attaching to teh db in question. So for this config, you need one
> host of the the single embedded dll to run and multiple people attaching to
> it.
> Hey that's called Superserver!
> Alan
>
>
Now I fully understand this issue.
I even discover that if firebird embedded would optionally create only
*one* superserver instance on the first loading into memory - it will be
a new feature ;)
All other applications will just use fbembed.dll as a client connecting
to existing embedded instance.
I'm sure this is difficult or there are obvious reasons why it can't
work that way.
I have in my mind such example: two applications - one which work on
database using GUI and one which just collect data from external device
and store in the same database.
Of course using SuperServer is a solution but someone could say that
embedded should allow such scenario also.
Regards
Boguslaw