on 1/31/04 7:39 PM, Robert Brenstein at rjb at rz DOT uni-potsdam.de wrote:
>>> -- simplify opening/creating encrypted database: New +
>>> Set(Structure)Encryption + Open --> CreateEncrypted and
>>> Set(Structure)Encryption + Open --> OpenEncrypted with Open returning
>>> an error dbEncrypted when trying to open an encrypted db. Also
>>> IsStructureEncrypted(fpath), IsDatabaseEncrypted(fpath) to check what
>>> kind of db we have (this was discussed on the list last year)
>>
>> Let's discuss this in separate thread.
>> And I did agree in the past with changes?
>> Just not sure it is possible simplify something.
>
> Search list archive for past discussions. No, you did not actually
> agree to do this. But yes, I still find these steps non-intuitive and
> more complicated than needed, particularly for programs that allow
> our users to have either encrypted or unencrypted databases. Now it
> is an opportunity to clean this up.
>
> Your current approach may be logical in VSDK but not in higher
> languages. I don't care what you do internally -- you can just call
> the current functions as they are.
Okay,
We have not yet work on encryption in 2.0
When we will start, let's think again on this
--
Best regards,
Ruslan Zasukhin [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan@paradigmasoft.com
web: http://www.paradigmasoft.com
To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------
_______________________________________________
Valentina mailing list
Valentina at lists DOT macserve.net
http://lists.macserve.net/mailman/listinfo/valentina
©2004 Ruslan Zasukhin |
