Need caching and archiving
As libj ends up being more and more complicated, there needs to be a location set for a given journal that:
1. Keeps an archive of journal entries and comments.
2. Keeps a record of the journal's information--account, server, MD5 hash of password. Should probably never even have the password stored plaintext in the library. MD5 of password seems sufficient for all even halfway secure methods of authentication.
3. In this way, when things get friended or their security changed, etc, the archive will also be updated. This will allow any programs to do more intensive operations off of the archive instead of repeatedly requesting each and every single entry.
4. If this is libj specific instead of program specific, the different programs using libj will be able to use the same archive for their bizness. That means LJClone, LJBunker, and FriendAll will be able to use the archives to do their work.
5. Will need a sync function that will download all changes and update
6. Will need a function to get list of entries and comment ids.
7. Will need a read in entry from archive function. Will need a read in from archive comment function.
Possibly should be looking into an embedded database for this...
http://java-source.net/open-source/database-engines
However, flatfile might be preferrable--more easily accessible in case things go wrong.
If using database, should definitely make a "Convert to HTML" or something. Should probably do that anyway.
But a flatfile wouldn't be too complicated, either.
archivedir
--account.info
--posts
--comments
--userpics
--polls
1. Keeps an archive of journal entries and comments.
2. Keeps a record of the journal's information--account, server, MD5 hash of password. Should probably never even have the password stored plaintext in the library. MD5 of password seems sufficient for all even halfway secure methods of authentication.
3. In this way, when things get friended or their security changed, etc, the archive will also be updated. This will allow any programs to do more intensive operations off of the archive instead of repeatedly requesting each and every single entry.
4. If this is libj specific instead of program specific, the different programs using libj will be able to use the same archive for their bizness. That means LJClone, LJBunker, and FriendAll will be able to use the archives to do their work.
5. Will need a sync function that will download all changes and update
6. Will need a function to get list of entries and comment ids.
7. Will need a read in entry from archive function. Will need a read in from archive comment function.
Possibly should be looking into an embedded database for this...
http://java-source.net/open-source/database-engines
However, flatfile might be preferrable--more easily accessible in case things go wrong.
If using database, should definitely make a "Convert to HTML" or something. Should probably do that anyway.
But a flatfile wouldn't be too complicated, either.
archivedir
--account.info
--posts
--comments
--userpics
--polls