On Wed, Apr 4, 2012 at 6:42 AM, Dmitry Yemanov <firebi...@yandex.ru> wrote:
>
> > 2. gfix -encrypt<plugin> {-cryptpar<parameter>} database
> > gfix passes plugin name and parameter in DPB, the rest of activity are
> > like in database validation. This implementation looks like most simple
> > to implement.
>
> No DPB hackery, please. GFIX could finally start doing something itself.
> For example, run ALTER DATABASE ENCRYPT asynchronously and show the
> progress (if requested) via querying the last encrypted pageno from the
> header. But anyway, this should be the secondary option, SQL is expected
> to be a primary tool for this task.
>
The design philosophy of InterBase was that our tools would not have any
secret
hooks into the engine so anyone could write tools that worked against the
database.
The DPB links for validating a database, etc. are not hackery in the sense
that they
were quick fixes that went contrary to the architecture. Gfix does a bit
of work itself
in resolving a two-phase commit, but the information is available to all
users. Gstat
is an obvious counter example - it reads the database without going through
the
engine.
And if I may put in one word about the encryption strategy, let me say
"on-line".
Slow performance beats no performance.
Best wishes,
Ann
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
