Hi Oli,
Am 22.03.2012 13:44, schrieb Oliver Welter:
>
> On 22.03.2012 12:27, Michael Bell wrote:
>
>> 1. Extend the DYNAMIC hash
>>
>> We need a key, a value and an operator. The problem with flexibility
>> is that it is difficult to imagine all the security implications.
>>
>> Old style:
>>
>> DYNAMIC->{"NAME"} = "Michael Bell"
>>
>> New style:
>>
>> DYNAMIC->{"NAME"}->{"VALUE"} = "Michael Bell"
>> DYNAMIC->{"NAME"}->{"OPERATOR"} = "EQUAL";
> I would go for that one - preferably with a "fallback" to the old form
> that results in an equal - that way we dont need to touch the old code
> except where we need another operator than equal. Dynamic currently
> accepts an array to create OR clauses, I guess that should be kept.
>
> Like is everything we need atm, support for not, less/greater and
> "less/greater or equal" would be nice.
Okay, I start implementing the following behaviour:
DYNAMIC->{"NAME"} = {"VALUE" => "Michael Bell", "OPERATOR" => "EQUAL"};
BTW do we prefer short git commits (which breaks the code) or long git
commits (which always result in working code)?
Best regards
Michael
--
___________________________________________________________________
Michael Bell Humboldt-Universitaet zu Berlin
Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice
Fax: +49 (0)30-2093 70135 Unter den Linden 6
[email protected] D-10099 Berlin
___________________________________________________________________
PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB
smime.p7s
Description: S/MIME Kryptografische Unterschrift
------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
