Quote:
Originally Posted by theonna
I'll give my Kobo order story, I have preordered on April 15th, 3 conversations with CS and 2 weeks worth of "processing"- I got shipping confirmation on May 6. CS kept telling me that there is very high demand and processing an order- is a lengthy process.
My friend placed her order on May 1st, when Aura was listed as in stock on the website, and still have not received a shipping confirmation.
As far as reader itself- it should ditch the database, and use normal file manager, would be by far more efficient and convenient. But why would anyone listen to me...
|
Considering the amount of information stored in the database, we would need to use a file system capable of storing a large amount of metadata in addition to the file name/size/data. At this point, I have difficulty thinking of one that has that capability and the near universal read-write availability of the FAT32 file system nor can I think of a consumer file system that is more efficient when searching and accessing stored information than a relational database.
The Mac HFS+ file system with data and resource forks or NTFS with streams are just not as universally supported as FAT32. Other possibilities suffer even more from a lack of operating system support. The only DBFS I can think of that could have reached the consumer was Microsoft's WinFS (one of the pillars of Windows Vista which vanished during the Vista reboot). There was the IBM DB2 for i which worked quite well but might be a touch difficult to port to a low power ereader.
Check out
Fortress Rochester by Frank G. Soltis for more on the topic.
Regards,
David