Files
evolution/camel
Not Zed 956b17ed95 changed order around, first try to delete and only remove from the object
2004-02-04  Not Zed  <NotZed@Ximian.com>

        * camel-store.c (camel_store_delete_folder): changed order around,
        first try to delete and only remove from the object bag if the
        delete worked.  If vjunk/vtrash enabled, don't allow those to be
        deleted.
        (cs_delete_cached_folder): helper to delete the folder if its in
        the cache, remove it from trash/junk, etc.
        (camel_store_unsubscribe_folder): changed similarly to
        delete_folder.

        * camel-vee-store.c (vee_delete_folder): dont do any trash/junk
        processing anymore.

2004-02-03  Not Zed  <NotZed@Ximian.com>

        * camel-store.c: use the folders object bag to manage the trash
        folder and junk folders.  Remove the init_trash and init_junk
        stuff, just use get_trash and get_junk to mean the same thing.
        Get rid of the hacked up vjunk and vtrash "uri" stuff too.

        * camel-object.c (camel_object_bag_add): null out the pair->func,
        otherwise we get an uninitalised memory read during unhook event.

svn path=/trunk/; revision=24603
2004-02-04 05:57:21 +00:00
..
2004-02-03 18:52:53 +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
2004-01-21 01:26:04 +00:00
2002-03-12 20:36:08 +00:00
2003-09-03 18:05:54 +00:00
2004-01-20 05:33:12 +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
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-01-16 18:13:04 +00:00
2004-01-16 18:13:04 +00:00
2004-01-16 18:13:04 +00:00
2004-01-27 04:13:10 +00:00
2003-12-01 22:51:58 +00:00
2003-03-20 19:37:38 +00:00
2003-10-16 15:33:47 +00:00
2004-01-20 05:33:12 +00:00
2002-06-03 02:56:35 +00:00
2004-01-29 08:24:16 +00:00
2004-01-29 08:24:16 +00:00
2004-01-23 17:16:47 +00:00
2004-01-20 05:33:12 +00:00
2003-03-28 00:13:46 +00:00
2002-05-24 20:14:59 +00:00
2002-07-31 01:03:10 +00:00
2002-07-31 01:03:10 +00:00
2004-01-05 20:55:29 +00:00
2002-06-03 02:56:35 +00:00
2003-03-06 14:39:30 +00:00
2003-06-09 17:31:26 +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.

....
...