Re: [firebird-support] Engine12 mistery
The way I think of the Y-valve* is that the stem of the Y is the client - whether the normal fbclient or the Java client or other language specific clients. The connection request goes from the client to a provider. Right now, the providers are Remote (which may be built into the Y-valve) and Engine12. Someone could create a provider that translated Firebird requests to Oracle/PostgreSQL/MySQL or whatever and offer a provider to a different back end. If there's enough demand, Firebird 2.5 could be cut back to be a provider to older versions of Firebird. So the stem is the client and the branches are the providers. Cheers, Ann * Y-valve is a nautical term. On a boat, the head (toilet) outflow goes through a Y-valve. One leg takes the effluent to a holding tank, the other dumps it overboard. No parallel implied between what goes through the Firebird Y-valve and the nautical term. On Tue, Jun 14, 2016 at 4:46 PM, fabia...@itbizolutions.com.au [firebird-support] <firebird-support@yahoogroups.com> wrote: > > > > Mark > > Thank you, I think I am beggining to understand the concept, so the > provider's have to be combined including ALWAYS Engine12 (the core FB > server procedure/method that really goes to the file on disk and does the > reading and writting to the DB). So the following combinations are valid: > Providers = Remote + Engine12 > Providers = Loopback + Engine12 > Providers = Remote + Loopback + Engine12 (the first two in any orther) > > And any Providers combination excluding Engine12 would not work because it > is not including the component that goes to the DB file and reads/writes > from /to it. > > It seems Engine12 is not the same "type of component" as the other > Providers. In the documentation it is refered as a Y valve, if I understand > it correctly Engine12 is the base of the Y, while the other providers are > the top left and top right of the Y, you can have any top you want, BUT YOU > MUST HAVE the base always, else it does not work, correct? > > > Cheers, > Fabian > > > > - Original Message - > *From:* Mark Rotteveel m...@lawinegevaar.nl [firebird-support] > <m...@lawinegevaar.nl+[firebird-support]> > *To:* firebird-support@yahoogroups.com > *Sent:* Wednesday, June 15, 2016 5:32 AM > *Subject:* Re: [firebird-support] Engine12 mistery > > On 2016-06-14 19:44, fabia...@itbizolutions.com.au [firebird-support] > wrote: > > My understanding from reading the documentation is: > > > > Provider = Remote means the client is on the network, excluding > > 127.0.0.1 > > Provider = Loopback means the client is actually on the same OS > > instance as the FB3 engine, and it is using the 127.0.0.1 to access > > the database to avoid the "embedded server concept" from answering > > the > > request, as it would capture the DB file and will not allow any other > > clients from remote /network source. > > Engine12 = The local server takes control of the database as if it > > was > > an embedded server, killing all future chance of accessing the DB > > from > > the network, so Engine12 is if I understand correctly the way to talk > > to the DB engine in "exclusive" mode when you want to perform > > maintenance or work on the security database. > > > > Is the above wrong? > > Yes, your understanding is wrong. Engine12 **is** the component that > actually does the work with the database file. The rest is just plumbing > to connect to servers (or make fbclient connect to a local server), > select the right provider, etc. > > As the release notes say: > > http://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-engine.html > > * Remote (establish network connection) > * Engine12 (main database engine) > * Loopback (force network connection to the local server for name> without an explicit network protocol being supplied). > > There was also talk of providing an 'Engine11' which would essentially > be a Firebird 2.5 you could use to connect to ODS 11.2 and older > database files. > > Your confusion likely stems from the fact that Firebird embedded now is > fbclient + Engine12, as opposed to Firebird server + Engine12 for a > normal database server, while Firebird embedded used to be a separate > DLL/SO. BTW: In normal situations fbclient **does not** have access to > Engine12, so it only behaves as a client library. > > Mark > > > > > Posted by: Mark Rotteveel <m...@lawinegevaar.nl> > > > ++ > > Visit http://www.firebirdsql.org and click the Documentation item > on the main (top) menu. Try FAQ and other links from the left-side menu > there. > > Also search the knowledgebases at > http://www.ibphoenix.com/resources/documents/ > > ++ > > > Yahoo Groups Links > > > > > > >
Re: [firebird-support] Engine12 mistery
15.06.2016 14:19, fabia...@itbizolutions.com.au [firebird-support] wrote: > When I omit Engine12 from the provider's list at the server's config, to > ensure the server > always acts as a super server This way you ensured that server cannot work with databases at all. I.e. it cannot work as a server. -- WBR, SD. ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/firebird-support/join (Yahoo! ID required) <*> To change settings via email: firebird-support-dig...@yahoogroups.com firebird-support-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: firebird-support-unsubscr...@yahoogroups.com <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
Re: [firebird-support] Engine12 mistery
Dimitry > No. Y-valve is fbclient.dll. It loads providers as configured. If you don't > need to > work with databases directly, you can omit Engine from list of providers. > Firebird server (fbserver.exe) uses fbclient.dll the same way as any other > application mmm, now we are back to my original question / problem. When I omit Engine12 from the provider's list at the server's config, to ensure the server always acts as a super server, and never acts as an embedded server, the clients from other computers cannot connect via tcp-ip (ip.ip.ip.ip:port/databasename); so why is engine12 needed as a provider at the server's config? (Everybody already answered that question saying because it is the engine of the database, but you are saying it is only the embedded engine of the DB, correct? Cheers, Fabian - Original Message - From: Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] To: firebird-support@yahoogroups.com Sent: Wednesday, June 15, 2016 6:56 PM Subject: Re: [firebird-support] Engine12 mistery 14.06.2016 22:46, fabia...@itbizolutions.com.au [firebird-support] wrote: > It seems Engine12 is not the same "type of component" as the other Providers. In the > documentation it is refered as a Y valve, if I understand it correctly Engine12 is the > base of the Y, while the other providers are the top left and top right of the Y, you can > have any top you want, BUT YOU MUST HAVE the base always, else it does not work, correct? No. Y-valve is fbclient.dll. It loads providers as configured. If you don't need to work with databases directly, you can omit Engine from list of providers. Firebird server (fbserver.exe) uses fbclient.dll the same way as any other application. -- WBR, SD. ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links
Re: [firebird-support] Engine12 mistery
14.06.2016 22:46, fabia...@itbizolutions.com.au [firebird-support] wrote: > It seems Engine12 is not the same "type of component" as the other Providers. > In the > documentation it is refered as a Y valve, if I understand it correctly > Engine12 is the > base of the Y, while the other providers are the top left and top right of > the Y, you can > have any top you want, BUT YOU MUST HAVE the base always, else it does not > work, correct? No. Y-valve is fbclient.dll. It loads providers as configured. If you don't need to work with databases directly, you can omit Engine from list of providers. Firebird server (fbserver.exe) uses fbclient.dll the same way as any other application. -- WBR, SD. ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/firebird-support/join (Yahoo! ID required) <*> To change settings via email: firebird-support-dig...@yahoogroups.com firebird-support-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: firebird-support-unsubscr...@yahoogroups.com <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
Re: [firebird-support] Engine12 mistery
Mark Thank you, I think I am beggining to understand the concept, so the provider's have to be combined including ALWAYS Engine12 (the core FB server procedure/method that really goes to the file on disk and does the reading and writting to the DB). So the following combinations are valid: Providers = Remote + Engine12 Providers = Loopback + Engine12 Providers = Remote + Loopback + Engine12 (the first two in any orther) And any Providers combination excluding Engine12 would not work because it is not including the component that goes to the DB file and reads/writes from /to it. It seems Engine12 is not the same "type of component" as the other Providers. In the documentation it is refered as a Y valve, if I understand it correctly Engine12 is the base of the Y, while the other providers are the top left and top right of the Y, you can have any top you want, BUT YOU MUST HAVE the base always, else it does not work, correct? Cheers, Fabian - Original Message - From: Mark Rotteveel m...@lawinegevaar.nl [firebird-support] To: firebird-support@yahoogroups.com Sent: Wednesday, June 15, 2016 5:32 AM Subject: Re: [firebird-support] Engine12 mistery On 2016-06-14 19:44, fabia...@itbizolutions.com.au [firebird-support] wrote: > My understanding from reading the documentation is: > > Provider = Remote means the client is on the network, excluding > 127.0.0.1 > Provider = Loopback means the client is actually on the same OS > instance as the FB3 engine, and it is using the 127.0.0.1 to access > the database to avoid the "embedded server concept" from answering > the > request, as it would capture the DB file and will not allow any other > clients from remote /network source. > Engine12 = The local server takes control of the database as if it > was > an embedded server, killing all future chance of accessing the DB > from > the network, so Engine12 is if I understand correctly the way to talk > to the DB engine in "exclusive" mode when you want to perform > maintenance or work on the security database. > > Is the above wrong? Yes, your understanding is wrong. Engine12 **is** the component that actually does the work with the database file. The rest is just plumbing to connect to servers (or make fbclient connect to a local server), select the right provider, etc. As the release notes say: http://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-engine.html * Remote (establish network connection) * Engine12 (main database engine) * Loopback (force network connection to the local server for without an explicit network protocol being supplied). There was also talk of providing an 'Engine11' which would essentially be a Firebird 2.5 you could use to connect to ODS 11.2 and older database files. Your confusion likely stems from the fact that Firebird embedded now is fbclient + Engine12, as opposed to Firebird server + Engine12 for a normal database server, while Firebird embedded used to be a separate DLL/SO. BTW: In normal situations fbclient **does not** have access to Engine12, so it only behaves as a client library. Mark Posted by: Mark Rotteveel <m...@lawinegevaar.nl> ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links
Re: [firebird-support] Engine12 mistery
On 2016-06-14 19:44, fabia...@itbizolutions.com.au [firebird-support] wrote: > My understanding from reading the documentation is: > > Provider = Remote means the client is on the network, excluding > 127.0.0.1 > Provider = Loopback means the client is actually on the same OS > instance as the FB3 engine, and it is using the 127.0.0.1 to access > the database to avoid the "embedded server concept" from answering > the > request, as it would capture the DB file and will not allow any other > clients from remote /network source. > Engine12 = The local server takes control of the database as if it > was > an embedded server, killing all future chance of accessing the DB > from > the network, so Engine12 is if I understand correctly the way to talk > to the DB engine in "exclusive" mode when you want to perform > maintenance or work on the security database. > > Is the above wrong? Yes, your understanding is wrong. Engine12 **is** the component that actually does the work with the database file. The rest is just plumbing to connect to servers (or make fbclient connect to a local server), select the right provider, etc. As the release notes say: http://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-engine.html * Remote (establish network connection) * Engine12 (main database engine) * Loopback (force network connection to the local server for without an explicit network protocol being supplied). There was also talk of providing an 'Engine11' which would essentially be a Firebird 2.5 you could use to connect to ODS 11.2 and older database files. Your confusion likely stems from the fact that Firebird embedded now is fbclient + Engine12, as opposed to Firebird server + Engine12 for a normal database server, while Firebird embedded used to be a separate DLL/SO. BTW: In normal situations fbclient **does not** have access to Engine12, so it only behaves as a client library. Mark
Re: [firebird-support] Engine12 mistery
My understanding from reading the documentation is: Provider = Remote means the client is on the network, excluding 127.0.0.1 Provider = Loopback means the client is actually on the same OS instance as the FB3 engine, and it is using the 127.0.0.1 to access the database to avoid the "embedded server concept" from answering the request, as it would capture the DB file and will not allow any other clients from remote /network source. Engine12 = The local server takes control of the database as if it was an embedded server, killing all future chance of accessing the DB from the network, so Engine12 is if I understand correctly the way to talk to the DB engine in "exclusive" mode when you want to perform maintenance or work on the security database. Is the above wrong? Thanks Fabian - Original Message - From: Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] To: firebird-support@yahoogroups.com Sent: Wednesday, June 15, 2016 4:19 AM Subject: Re: [firebird-support] Engine12 mistery 14.06.2016 19:56, 'Mark Rotteveel' m...@lawinegevaar.nl [firebird-support] wrote: > Is there a reason why the FB 3 server configured as follows would require Engine12 as a > provider? Because it is server. The configuration is enough for Firebird client, but server needs engine to work with databases. -- WBR, SD. ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links
Re: [firebird-support] Engine12 mistery
14.06.2016 19:56, 'Mark Rotteveel' m...@lawinegevaar.nl [firebird-support] wrote: > Is there a reason why the FB 3 server configured as follows would require > Engine12 as a > provider? Because it is server. The configuration is enough for Firebird client, but server needs engine to work with databases. -- WBR, SD. ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/firebird-support/join (Yahoo! ID required) <*> To change settings via email: firebird-support-dig...@yahoogroups.com firebird-support-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: firebird-support-unsubscr...@yahoogroups.com <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
Re: [firebird-support] Engine12 mistery
Engine12 is actually the post of Firebird 3 that is the implementation of the database server (and understands ODS12). So it is a required part of Firebird 3. Mark - Bericht beantwoorden - Van: "fabia...@itbizolutions.com.au [firebird-support]" <firebird-support@yahoogroups.com> Aan: <firebird-support@yahoogroups.com> Onderwerp: [firebird-support] Engine12 mistery Datum: di, jun. 14, 2016 19:36 Hi All, Is there a reason why the FB 3 server configured as follows would require Engine12 as a provider? DatabaseAccess = NoneAuthServer = SrpAuthClient = SrpUserManager = SrpProviders = RemoteWireCrypt = Enabled WireCompression = falseServerMode = Super I've noticed the network applications that access the FB3 db failed to connect unless I add the Engine12 to the providers list, would that be because FB3 engine needs Engine12 to access the security DB at the handshake? The way the network apps try to talk to the FB3 server is via ODBC and the database field is defined as 192.168.xxx.xxx:MyDbName , I also tried with 192.168.xxx.xxx/3050:MyDbName and made no difference, any ide why Engine12 is required? Cheers, Fabian
[firebird-support] Engine12 mistery
Hi All, Is there a reason why the FB 3 server configured as follows would require Engine12 as a provider? DatabaseAccess = None AuthServer = Srp AuthClient = Srp UserManager = Srp Providers = Remote WireCrypt = Enabled WireCompression = false ServerMode = Super I've noticed the network applications that access the FB3 db failed to connect unless I add the Engine12 to the providers list, would that be because FB3 engine needs Engine12 to access the security DB at the handshake? The way the network apps try to talk to the FB3 server is via ODBC and the database field is defined as 192.168.xxx.xxx:MyDbName , I also tried with 192.168.xxx.xxx/3050:MyDbName and made no difference, any ide why Engine12 is required? Cheers, Fabian
