MobileRead Forums - View Single Post

devils_add · 12-17-2013, 05:46 PM

Guys, you are forgetting about the DMG file extension in Apple. Where everything the program needs to run is inside that file (which is an archive). So, what I am proposing is to have just the met file associated with record and record itself inside the archive which will be added into the main database. The only time the archive is written to is when files are added or when metadata is changed, and all other times it is opened is to extract a needed file to read it or to send it to the device.
Therefore, the main database file will be outside as it is right now. Also, you can have the main database link to virtual libraries databases for different, incompatible formats. In addition, this will allow for creating a single database for everything, with different iteration on front-end. So that you can have all your collections managed by just one database.
Sorry, for wordiness.

Also, with the archive architecture, you can keep some pdf books broken by chapter, and combine them on the fly as requested (resources available), so you don't have to download the full book, but just the chapters you need.

12-17-2013, 05:46 PM	#8
devils_add Member Posts: 13 Karma: 10 Join Date: Sep 2013 Device: none	Guys, you are forgetting about the DMG file extension in Apple. Where everything the program needs to run is inside that file (which is an archive). So, what I am proposing is to have just the met file associated with record and record itself inside the archive which will be added into the main database. The only time the archive is written to is when files are added or when metadata is changed, and all other times it is opened is to extract a needed file to read it or to send it to the device. Therefore, the main database file will be outside as it is right now. Also, you can have the main database link to virtual libraries databases for different, incompatible formats. In addition, this will allow for creating a single database for everything, with different iteration on front-end. So that you can have all your collections managed by just one database. Sorry, for wordiness. Also, with the archive architecture, you can keep some pdf books broken by chapter, and combine them on the fly as requested (resources available), so you don't have to download the full book, but just the chapters you need. Last edited by devils_add; 12-17-2013 at 05:48 PM.