There is a critical problem with the design of IndexClient. When
using dates, IndexClient assumes that the date is the current date
(UTC/GMT, of course). This is fine when inserting files into
something like a newsgroup or mailbox, but it is horribly unsuitable
when requesting items from a newsgroup or mailbox or whatever. The
reason is that it does not allow items from previous days which have
not been downloaded yet to be read. If you download some items one
day, and then download more items the next day, all the items posted
the previous day after the last downloaded will not be downloaded (and
will seem to not exist). This is quite a problem if you are not
running something like a freenet-news/NNTP gateway constantly.
What would be better is if the last date and index is specified to
IndexClient when instantiating it, and then it would keep track of the
latest item date and index read and the present latest date and
index. It would automatically handle inserting items at the correct
date and index, and would automatically handle rolling over dates
(after a threshold of consecutive nonexistent items are requested for
a certain day, a rollover to the next day and an index of 0 is done if
the day being read is before the present day). This would make using
IndexClient much easier, and would eliminate the problem described in
the previous paragraph.
--
Yes, I know my enemies.
They're the teachers who tell me to fight me.
Compromise, conformity, assimilation, submission, ignorance,
hypocrisy, brutality, the elite.
All of which are American dreams.
- Rage Against The Machine
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 1528 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20010504/8409f904/attachment.pgp>
