Re: [WebDNA] WebDNA 8.2 and BioType
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 112589
interpreted = N
texte = 171 > We could imagine the database would run NOT encrypted from RAM > (to allow regular database operations), and that each time > WebDNA needs to update the disk, it builds an encrypted copy: > this is this copy that would be written to disk. There would be > a speed impact only when writing to or reading from disk. This would be ideal. To make this even better, why not add a feature that also allows us to decide which dbs will be automatically encrypted on disk and decrypted when they are read into RAM ... Perhaps WebDNA could do the automatic encryption/decryption only when the string "encrypted" appears in the database name? This would be a practical way for us as programmers to know which dbs are encrypted, and also for the WebDNA engine to know which dbs it should encrypt/decrypt. > I wonder if you cannot already build something like that with > the current tools. We cannot accomplish this on a practical basis ourselves. I've given this a lot of thought. There are too many limitations to deal with, and some of them simply cannot be overcome by the use of the WebDNA language and the OS tools. Plus this should not require us as programmers to "jump through a bunch of hoops" in order to have our dbs encrypted. The whole idea here is to give us a super-simple (and preferably automatic) method for encrypting all the data in our dbs. The best way to do it, in my opinion, would be to rewrite the WebDNA engine so that it performs the encryption/decryption automatically at the proper times, and only on the specified dbs. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
171 > We could imagine the database would run NOT encrypted from RAM > (to allow regular database operations), and that each time > WebDNA needs to update the disk, it builds an encrypted copy: > this is this copy that would be written to disk. There would be > a speed impact only when writing to or reading from disk. This would be ideal. To make this even better, why not add a feature that also allows us to decide which dbs will be automatically encrypted on disk and decrypted when they are read into RAM ... Perhaps WebDNA could do the automatic encryption/decryption only when the string "encrypted" appears in the database name? This would be a practical way for us as programmers to know which dbs are encrypted, and also for the WebDNA engine to know which dbs it should encrypt/decrypt. > I wonder if you cannot already build something like that with > the current tools. We cannot accomplish this on a practical basis ourselves. I've given this a lot of thought. There are too many limitations to deal with, and some of them simply cannot be overcome by the use of the WebDNA language and the OS tools. Plus this should not require us as programmers to "jump through a bunch of hoops" in order to have our dbs encrypted. The whole idea here is to give us a super-simple (and preferably automatic) method for encrypting all the data in our dbs. The best way to do it, in my opinion, would be to rewrite the WebDNA engine so that it performs the encryption/decryption automatically at the proper times, and only on the specified dbs. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Virtual Postcards (1998)
Webcat and logging (1998)
WC2.0 Memory Requirements (1997)
Proper file locations (1997)
Re[2]: OT: Amazon Patents (2000)
Merchant account (1998)
another problem (1997)
So, does anyone have developer editon running on Win XP (2006)
Affiliate Marketing Question #2 (1998)
WebCat2 - many [carts] on one template page? (1997)
Weird Problem (1997)
Date Range search (1997)
Web Catalog 2 demo (1997)
Date math (1997)
Lost and Recovered. (1998)
date pref (1999)
emailer w/F2 (1997)
upgrade? (1997)
off-topic - printinglib 68K (1997)
international time (1997)