Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

10
  • Well, if I'll go with the block system, pulling the record out of DB by a primary key would be faster than searching a directory of thousands of files. As for the cookies, I'm thinking of re-setting the cookies on each page view, with a eg 10min expiry, so that after 10min inactivity a re-login is required. I need to store the decrypted key somewhere, else the user would have to enter their password on each page view. Commented Feb 21, 2013 at 22:17
  • To get the pk dosen't the user first have to click on the record he wants.. that means you need to first show him a record set... that means either displaying all the data or querying (reading) all the data.. that means decrypting all the data.... Commented Feb 21, 2013 at 22:44
  • Yes, all the data for the same user... What I wanted was a MySQL table with user id, data block for every user. Commented Feb 21, 2013 at 22:46
  • 1
    Well, the main requirement is data security, speed comes second. The main "scaling factor" here will be user number - each user will only have 100-200 records, so decrypting that data block shouldn't be too bad. As for user number, that will hopefully scale with the MySQL, and if it goes over a few thousand, I guess I'll look at more efficient solutions then. Commented Feb 21, 2013 at 22:50
  • 2
    Al relational Dbs, mysql included a optimized to pull data by use of indexes.. I need to blog about this.. it comes up way too often Commented Feb 21, 2013 at 23:07