Files
evolution/camel
Jeffrey Stedfast b27eb5f67a Set summary equal to NULL. (imap_get_summary): Store the summary in the
2000-06-19  Jeffrey Stedfast  <fejj@helixcode.com>

	* providers/imap/camel-imap-folder.c (camel_imap_folder_init):
	Set summary equal to NULL.
	(imap_get_summary): Store the summary in the ImapFolder
	(imap_summary_get_by_uid): If we have a summary cache in the
	ImapFolder, first check to see if that message info is in the
	cached summary first, if not fetch it directly from the IMAP
	server and append it to the summary cache.
	(imap_get_message_flags): Don't free the message info that we
	get back from summary_get_by_uid as we don't want to be
	corrupting our cached summary.

svn path=/trunk/; revision=3636
2000-06-19 20:54:50 +00:00
..
2000-06-07 23:57:18 +00:00
2000-06-02 06:34:58 +00:00
2000-05-18 22:40:24 +00:00
2000-04-18 19:05:15 +00:00
2000-06-12 22:32:54 +00:00
2000-05-23 02:57:31 +00:00
2000-06-12 22:32:54 +00:00
2000-05-17 04:08:41 +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-29 11:09:32 +00:00
2000-05-07 21:56:32 +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.

....
...