I agree. I also think better MIME support would be a good thing.
>>Ive started doing the same type of thing in C++.
>
>My profesional experience is in C++, I thought I'd do this
>in Java as a learning experience. I'd probably find it
>easier to write the base classes in C++, I'm more used to
>C++ streams than Java ones.
>
OK. I only really started in C++ cause its also the lang I am
comforatable with.
>>Need a hand ?
>
>You mentioned you were investigating file formats, I have a few
>of them, but right now I don't know how the history.pag
>and history.dir files are put together.
>
Hmmm. History.pag was documented at that web site, dont have a URL
at the moment. However I have been working from this
Notes on History.pag
history.pag so far known by me:
- divided into 2 k blocks (0x0800 = 2048)
- first two bytes of block tell how much following data is used in
that block
- third byte is the length of the first Message-ID
- then the message-ID
- first byte after Message-ID tells length of extra data following
- data follow message-ID (12 bytes it seems always)
- first 4 bytes big endian news.dat offset to the USED value of
header.
- second 4 bytes maybe date imported (not sure of format,
probably
number of minutes from some date)
- last 4 bytes is a 'supercedes' date, or 0 if none
- the message-ID's in each block are sorted alphabetically,
seemingly
As far as I can see this description is pretty right for
history.pag. I have not verified that the offsets into news.dat
are correct, but I assume they are cause everything else is.
The history.dir file(and the readart.dir file) are both unknown to
me at the moment. I assume they are as there name suggests some
kind of directory of the .pag files.
The one I am currently working on is the overview files. Ive
worked out 90% of this file but some of the bytes at the end of
the articale structure are a puzzle.
Anyone else worked this one out ?
Cheers,
Ciaran
-- We should flee in terror... Yes that would be the wisest course ciaran@dynamite.com.au