On 8/7/06, Lars Heuer <[EMAIL PROTECTED]> wrote:
Hi Robert,
[...]
>> Additionally I am interested in a good XML format for msgs.
[...]
> i suspect that the hardest part of the problem will be defining
> exactly that good means in this context. any initial thoughts?
We've collected some resources here:
<http://restlet.tigris.org/issues/show_bug.cgi?id=138>
aHa!
i see the connection now :-)
one of the main reasons why i want to use webDAV is that it's RESTful.
IMAP and POP3 both suck for the problems i'm interested in because
they are not.
IMHO email is basically authoring and so is a good match for webDAV.
i'd be interested to hear your thoughts on the way you planned to map
common email operations to RESTful operations.
The most advanced solution I am aware of is documented here:
XML For Digital Preservation: XML Implementation Options for E-Mails
<http://www.digitaleduurzaamheid.nl/bibliotheek/docs/email-xml-imp.pdf>
what are the advantages of using xml?
>> Well, I want to use Restlet (http://www.restlet.org/) and connect it
>> to a 'normal' POP3 / IMAP4 account a provide a restful view on it.
> probably the easiest way to do this would be by using javamail to
> provide a transparent layer on top of those protocols.
Yes that are also my thoughts. Not sure if JavaMail is the best lib,
though. I am evaluating Ristretto
<http://www.columbamail.org/drupal/?q=node/18>. It is a subproject of
Columba, a Java e-mail client (<http://www.columbamail.org>).
thanks for the URL - looks good. i'll have to take a deeper look...
javamail has the advantage of being written by committee. they cover
all the bases of existing email systems but their approach is only
extensible within their chosen paradigm. i found it very worthwhile to
review the specification.
- robert
