aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/white-papers/mail/ChangeLog6
-rw-r--r--doc/white-papers/mail/camel.sgml8
2 files changed, 14 insertions, 0 deletions
diff --git a/doc/white-papers/mail/ChangeLog b/doc/white-papers/mail/ChangeLog
index 93bc1fd755..0a9b744cd7 100644
--- a/doc/white-papers/mail/ChangeLog
+++ b/doc/white-papers/mail/ChangeLog
@@ -1,3 +1,9 @@
+2000-02-28 bertrand <bertrand@helixcode.com>
+
+ * camel.sgml: add a blurb about camel offering
+ uniform interface. needs style and grammar corrections.
+
+
2000-02-28 Dan Winship <danw@helixcode.com>
* camel.sgml: Beginnings of a Camel white paper
diff --git a/doc/white-papers/mail/camel.sgml b/doc/white-papers/mail/camel.sgml
index c3471059b1..ec8f5f70c6 100644
--- a/doc/white-papers/mail/camel.sgml
+++ b/doc/white-papers/mail/camel.sgml
@@ -52,6 +52,14 @@
<title>Overview</title>
<para>
+ Camel sees all mail repositories as stores containing
+ folders. These folders in turn contain the messages
+ the client actually accesses. The use of such a unified
+ interface allows the client applications to be very
+ extensible. Camel includes a provider mechnism which
+ allows the application to be written once, and access
+ the various mail protocols when camel supports them.
+ <para>
To begin using &Camel;, an application first creates a
<classname>CamelSession</classname> object. This object is used
to store application defaults, and to coordinate communication