Files
evolution/camel
NotZed aa7851f1f0 And same here ...
2000-05-05  NotZed  <NotZed@HelixCode.com>

        * camel-folder-summary.c: And same here ...

        * camel-mime-utils.c: Defined out some memory profiling stuff I
        left there by mistake.

        * camel-mime-parser.c (folder_scan_content): Apply the fix from
        the header scanner to here too.
        (folder_scan_header): Only check for end of header if we have
        space for it (didn't end the read with a newline)
        (folder_scan_header): inptr is the only real thing we need
        registerised for performance.  Try to help the compiler be smart
        about it ..
        (folder_scan_header): Simplified the save header case a tad.

        Commented out some memory profiling stuff.

svn path=/trunk/; revision=2811
2000-05-05 08:47:02 +00:00
..
2000-05-05 08:47:02 +00:00
2000-03-28 21:12:12 +00:00
2000-05-02 23:22:33 +00:00
2000-05-05 08:47:02 +00:00
2000-04-29 15:57:54 +00:00
2000-04-29 15:57:54 +00:00
2000-04-18 19:05:15 +00:00
2000-05-05 08:47:02 +00:00
2000-05-05 08:47:02 +00:00
2000-05-05 08:47:02 +00:00
2000-05-05 08:47:02 +00:00
2000-04-18 19:05:15 +00:00
2000-04-18 19:05:15 +00:00
2000-04-18 19:05:15 +00:00
2000-04-18 19:05:15 +00:00
2000-05-02 23:08:20 +00:00
2000-05-05 08:47:02 +00:00
1999-11-26 13:05:15 +00:00
2000-02-16 15:42:48 +00:00
1999-08-29 22:13:34 +00:00

                                   CAMEL
     

			A generic Messaging Library


                                   ----
				

Introduction:
-------------

Camel will be a generic messaging library. It will evntually support 
the standard messaging system for receiving and sending messages.
It aims at being the backend for the future gnome-mailer system.

The name "camel" stands for ... nothing. Open area of development there.
You know, that "bazaar" thing. Maybe could we organize a big contest on
gnome-list to find the best explanation :)

Camel draws heavily from JavaMail and the IMAP4rev1 RFC. People
wanting to hack on a provider should read the JavaMail API
specification, but CMC and MAPI are of interest too.

Please, before starting anything, wait for me to finish the abstract
classes. Some parts are not definitive yet.

 
Organization:
-------------

The library is roughly a set of abstract classes, some kind of generic
"interfaces" (idl interfaces, not java interfaces ).

Particular implementations are called providers.

Here are the basic objects:

* CamelService : an abstract class representing an access to a server.
Handles the connection and authentication to any server.

* CamelStore (CamelService): A hierarchy of folders on a server.

* CamelFolder : An object containing messages. A folder is always
associated with a store.

* CamelMessage : An object contained in folders. Is defined by a set
of attributes and a content. (Attributes include: the date it was
received, the sender address, .....)

* CamelTransport (CamelService): A way to send messages.

....
...