Files
evolution/camel
Jeffrey Stedfast 7acecd99c9 Rewrote to take a third argument (gboolean *selectable) so that we can
2000-09-13  Jeffrey Stedfast  <fejj@helixcode.com>

	* providers/imap/camel-imap-store.c (imap_folder_exists): Rewrote
	to take a third argument (gboolean *selectable) so that we can
	find out if the folder is selectable or not as we look to see if
	it exists. Also, don't use EXAMINE because that will not work on
	non-selectable folders, so use LIST instead.
	(get_folder): Check to see if the folder exists even vefore
	calling imap_create as this will save time. If the folder does
	exist, find out if it's selectable. Moved the call to refresh_info
	here.

	* providers/imap/camel-imap-folder.c (imap_get_uids): Check for a
	NULL summary.
	(camel_imap_folder_new): Don't call refresh_info here - call it in
	get_folder() because we don't know if this folder even exists on
	the server yet! And even if it does, we don't know if it can hold
	messages or not yet.

svn path=/trunk/; revision=5412
2000-09-13 22:13:09 +00:00
..
2000-06-07 23:57:18 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-25 04:31:13 +00:00
2000-08-10 17:30:50 +00:00
2000-08-11 02:57:11 +00:00
2000-08-10 17:30:50 +00:00
2000-08-11 02:57:11 +00:00
2000-08-11 02:57:11 +00:00
2000-09-07 03:48:39 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-25 04:31:13 +00:00
2000-08-10 17:30:50 +00:00
2000-08-11 02:57:11 +00:00
2000-08-11 02:57:11 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-16 18:33:20 +00:00
2000-08-10 17:30:50 +00:00
2000-06-22 21:51:40 +00:00
2000-09-07 21:00:56 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-11 02:57:11 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-05-29 11:09: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.

....
...