Files
evolution/camel
Jeffrey Stedfast e74803511e These fixes make it so that the CamelStore does not actually hold a ref on
2001-03-08  Jeffrey Stedfast  <fejj@ximian.com>
	These fixes make it so that the CamelStore does not actually hold
	a ref on it's vTrash folder. The vTrash folder is now created ONLY
	when it is requested. This solves the problem of not being able to
	unref a Store and have it disconnect/finalize like we expect it to.

	* camel-store.c (init_trash): When we create the vtrash, add all
	previously opened folders to it and hook on to the finalize event
	so that we can then set the store->vtrash to NULL.
	(get_trash): If a vtrash folder for the store doesn't exist,
	init_trash() and then try.
	(construct): No longer need this.
	(camel_store_class_init): Don't override the construct method.
	(camel_store_finalize): We no longer hold a ref on the vtrash so
	don't unref it.

svn path=/trunk/; revision=8595
2001-03-08 20:01:42 +00:00
..
2001-02-08 03:53:15 +00:00
2001-01-22 11:57:29 +00:00
2000-11-24 03:18:20 +00:00
2001-01-17 01:07:02 +00:00
2000-11-29 10:49:05 +00:00
2000-11-16 06:13:22 +00:00
2000-11-24 03:18:20 +00:00
2001-02-06 04:33:47 +00:00
2000-11-21 22:04:40 +00:00
2001-02-21 20:30:29 +00:00
2001-01-25 05:10:59 +00:00
2001-02-21 20:30:29 +00:00
2000-11-14 21:29:21 +00:00
2001-03-01 06:15:03 +00:00
2001-02-21 20:30:29 +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.

....
...