Re: [binarycloud-dev] revised entity def format...

[Alex B. <en...@tu...>]

> Wouldn't this be better accomplished with a user-definable field-type with an
> associated I/O class..having a tag called "encrypt" seems too simplistic to
> really provide any meaningful encryption service..

For example: we'll have systeic control over encryption settings, but I
think it's safe to assume that a developer would want to use the same key
length and settings for all the fields (as it would be a nightmare to
maintain a key per field, etc)

in the entity definition, encryption is as simple as "encrypt" ... elsewhere
we'll have very fine control over what exactly happens as a result.

...

We will have an I/O class if I read manuel's previous message correctly, and
that will load a configuration file. probably called conf/Encryption.php or
something :)

does that make sense or did I miss your point?

_alex