From 1e56ca6288490a924dfdfaf81618fa940ae807e7 Mon Sep 17 00:00:00 2001 From: bertrand Date: Mon, 28 Feb 2000 17:14:53 +0000 Subject: add a blurb about camel offering uniform interface. needs style and 2000-02-28 bertrand * camel.sgml: add a blurb about camel offering uniform interface. needs style and grammar corrections. svn path=/trunk/; revision=1976 --- doc/white-papers/mail/ChangeLog | 6 ++++++ doc/white-papers/mail/camel.sgml | 8 ++++++++ 2 files changed, 14 insertions(+) (limited to 'doc/white-papers') 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 + + * camel.sgml: add a blurb about camel offering + uniform interface. needs style and grammar corrections. + + 2000-02-28 Dan Winship * 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 @@ -51,6 +51,14 @@ Overview + + 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. To begin using &Camel;, an application first creates a CamelSession object. This object is used -- cgit v1.2.3