Postby dwerthmu » Thu Aug 30, 2007 9:33 am
Sorry my view of an archive is an open format. An Archive can not use proprietary formats if its to live a long time.
I see the API documentation has lots of info in creating new items, but don't see anything about reading whats there.
I stand corrected - at the top of the API document there is info about accessing the mailbox
Are there Any other sources for info about the API Like java code samples using Axis 2 or something like that?
The problem with just using the archiving feature is that it keeps everything, and is missing the organization that a user imposes. Everything we do here is a project, people organize items in a their own project folders. The archiver would not know what message goes with what project. I could see the archiver tool being useful to us if a user could submit a already existing folder to the archive. Like when the project is done.
Ideas?