This session will be devoted to the architecture of Firebird 3: The Interface-based API of plugins, and its configuration (which can be done separately for each database) OSRI (Open Systems Relational Interface) implementation with plugins (more details about OSRI) Non-SQL stored procedures and triggers with plugins Safe passwords and network encryption Trace plugin and more Who would be interested in this topic? The plugins API in Firebird 3 is designed to significantly improve the capabilities of embedding external code. There will be areas of extension which will allow the following: external triggers and procedures (written in almost any programming language) custom trace plugins security plugins to implement custom users identification (biometrics, etc) traffic encryption using algorithms others than SHA1 and RC4 Special attention will be devoted to non-standard providers, such as bridges to external (non-Firebird) databases or ODBC connection and caching abilities.

1. Firebird 3: provider-based architecture, plugins and OO approach to API Alex Peshkov Firebird Foundation 2011

3. Providers – based architecture (OSRI) Providers Clients YValve Network listener User program (isql, php, etc.) Engine8_11 Engine12 Network redirector

4. Server with additional provider Providers Clients YValve Network listener ODBC gate Engine12

6. Client with additional provider Providers Clients YValve User program Engine12 Cache Network redirector

26. Interfaces hierarchy IVersioned IMaster IDisposable IRefCounted IPluginBase IPluginFactory IStatus IPluginConfig IService IProvider ExternalEngine

43. Provider's interfaces IProvider attachService() attachDatabase() startTransaction() allocateStatement() IAttachment compileRequest() openBlob() queEvents() IService ITransaction IStatement getParameters() IRequest IBlob IEvents IParameters Metadata

73. Thanks for your attention!