diff options
| author | bertrand <bertrand@helixcode.com> | 2000-02-29 01:14:53 +0800 |
|---|---|---|
| committer | Bertrand Guiheneuf <bertrand@src.gnome.org> | 2000-02-29 01:14:53 +0800 |
| commit | 1e56ca6288490a924dfdfaf81618fa940ae807e7 (patch) | |
| tree | c41124021bbc3d573a889787a8ef4debc8f4cd4f | |
| parent | e047685e4a4ac36ea34b7108fbbc7612384e206d (diff) | |
| download | gsoc2013-evolution-1e56ca6288490a924dfdfaf81618fa940ae807e7.tar.gz gsoc2013-evolution-1e56ca6288490a924dfdfaf81618fa940ae807e7.tar.zst gsoc2013-evolution-1e56ca6288490a924dfdfaf81618fa940ae807e7.zip | |
add a blurb about camel offering uniform interface. needs style and
2000-02-28 bertrand <bertrand@helixcode.com>
* camel.sgml: add a blurb about camel offering
uniform interface. needs style and grammar corrections.
svn path=/trunk/; revision=1976
| -rw-r--r-- | doc/white-papers/mail/ChangeLog | 6 | ||||
| -rw-r--r-- | doc/white-papers/mail/camel.sgml | 8 | ||||
| -rw-r--r-- | help/white-papers/mail/ChangeLog | 6 | ||||
| -rw-r--r-- | help/white-papers/mail/camel.sgml | 8 |
4 files changed, 28 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 diff --git a/help/white-papers/mail/ChangeLog b/help/white-papers/mail/ChangeLog index 93bc1fd755..0a9b744cd7 100644 --- a/help/white-papers/mail/ChangeLog +++ b/help/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/help/white-papers/mail/camel.sgml b/help/white-papers/mail/camel.sgml index c3471059b1..ec8f5f70c6 100644 --- a/help/white-papers/mail/camel.sgml +++ b/help/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 |