Subject | Re: [Firebird-Architect] Re: Engine information (nr. of attachments, databases, db-name-info) for vulcan |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2006-05-08T16:19:49Z |
On 8 May 2006 at 10:55, Roman Rokytskyy wrote:
provider gets all necessary information from function call
parameters.
Only dispatcher knows everything because it has to translate
external handles into internal handles and vice versa.
Dispatcher can scan it's internal tables and collect information
from every provider mentioned there.
--
SY, Dimitry Sibiryakov.
>Each provider knows its open databases, right?No. It _may_ keep this list somewhere in global memory but normally
provider gets all necessary information from function call
parameters.
Only dispatcher knows everything because it has to translate
external handles into internal handles and vice versa.
Dispatcher can scan it's internal tables and collect information
from every provider mentioned there.
>It also knows the corresponding accounts, right?Right. But only if you tell him which connection you have in mind.
>The Classic mode is not very good example, since the fb_inet_server orI meant Vulcan classic mode: non-shared cache.
>inetd are not interested in answering any question - they simply map
>data streams.
--
SY, Dimitry Sibiryakov.