Files
evolution/camel
Jeffrey Stedfast 458b72a844 Don't allow users to create folders in offline mode. When in offline mode,
2004-10-20  Jeffrey Stedfast  <fejj@ximian.com>

	* providers/imap4/camel-imap4-store.c (imap4_get_folder): Don't
	allow users to create folders in offline mode. When in offline
	mode, use a different codepath to get a folder object.
	(imap4_noop): Handle offline mode.
	(imap4_unsubscribe_folder): Throw an exception if we are in
	offline mode.
	(imap4_subscribe_folder): Same.
	(imap4_get_folder_info): Started to implement offline
	support. Also, even if we are in online mode but the engine has
	not yet been connected, we should follow the "offline" code path
	and get the folder info's from the cache.
	(imap4_rename_folder): Disallow in offline mode.
	(imap4_delete_folder): Same.
	(imap4_connect): Handle offline mode.
	(imap4_disconnect): Handle offline mode and do proper locking.
	(imap4_query_auth_types): Same.

svn path=/trunk/; revision=27660
2004-10-20 19:39:44 +00:00
..
2002-03-25 21:47:36 +00:00
2002-03-01 21:39:17 +00:00
2003-04-19 03:15:54 +00:00
2002-03-12 20:36:08 +00:00
2004-02-16 09:38:24 +00:00
2004-09-27 05:30:11 +00:00
2004-09-27 05:30:11 +00:00
2004-09-24 02:50:45 +00:00
2002-11-07 21:34:17 +00:00
2003-03-28 00:13:46 +00:00
2003-03-06 14:47:05 +00:00
2004-01-16 18:13:04 +00:00
2002-03-01 21:39:17 +00:00
2001-10-27 16:59:46 +00:00
2001-10-27 16:59:46 +00:00
2001-10-27 16:59:46 +00:00
2004-09-27 05:30:11 +00:00
2001-10-27 16:59:46 +00:00
2002-03-01 21:39:17 +00:00
2003-06-25 10:20:09 +00:00
2003-03-06 14:39:30 +00:00
2003-03-06 14:39:30 +00:00
2002-07-11 22:30:51 +00:00
2002-03-01 21:39:17 +00:00
2002-03-01 21:39:17 +00:00
2002-03-01 21:39:17 +00:00
2004-03-15 14:37:47 +00:00
2004-10-12 02:01:22 +00:00
2004-08-12 16:33:25 +00:00
2004-09-27 05:30:11 +00:00
2001-10-27 16:59:46 +00:00
2004-09-27 05:30:11 +00:00
2004-05-03 07:48:46 +00:00
2004-07-14 19:00:37 +00:00
2004-09-24 02:50:45 +00:00
2003-03-20 19:37:38 +00:00
2004-09-24 02:50:45 +00:00
2002-06-03 02:56:35 +00:00
2004-09-24 02:50:45 +00:00
2004-09-20 08:38:58 +00:00
2004-05-26 04:24:01 +00:00
2001-10-27 16:59:46 +00:00
2001-10-27 16:59:46 +00:00
2004-03-15 14:37:47 +00:00
2001-10-27 16:59:46 +00:00
2004-09-24 02:50:45 +00:00
2004-09-24 02:50:45 +00:00
2004-09-24 02:50:45 +00:00
2004-09-24 02:50:45 +00:00
2004-09-27 05:30:11 +00:00
2004-01-05 20:55:29 +00:00
2004-02-27 06:08:04 +00:00
2003-06-09 17:31:26 +00:00
2002-01-02 23:04:06 +00:00

                                   CAMEL
     

			A generic Messaging Library


                                   ----
				

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

Camel is a generic messaging library. It supports the standard 
messaging system for receiving and sending messages. It is the 
messaging backend for Evolution.

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.

 
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.

....
...