Files
evolution/camel
6 8e7d0e31cb Thread function to perform filtering. (filter_free): Free the filter
2001-09-06    <NotZed@Ximian.com>

	* providers/imap/camel-imap-folder.c (filter_proc): Thread
	function to perform filtering.
	(filter_free): Free the filter object.
	(camel_imap_folder_changed): If we have threads enabled, then
	queue up a request to perform filtering.  For bug #4422.

	* providers/imap/camel-imap-store.c (camel_imap_msg_new): Create a
	new 'imap msg'.
	(camel_imap_msg_queue): Queue an 'imap msg'.
	(async_received): Handle receiving of imap msg in async thread.
	(async_destroy): Handle destroying of imap msg.
	(camel_imap_store_finalize): Destroy thread when done.
	(camel_imap_store_init): Setup thread.

	* providers/imap/camel-imap-store.h: Added an ethread to the
	store, for async processing.

svn path=/trunk/; revision=12666
2001-09-07 01:19:47 +00:00
..
2001-09-04 19:51:45 +00:00
2001-08-27 18:28:06 +00:00
2001-07-17 16:08:47 +00:00
2001-07-17 16:08:47 +00:00

                                   CAMEL
     

			A generic Messaging Library


                                   ----
				

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

[ NB. Camel has been written now. Please convert future tense to
present tense. Thank you.

	-- Peter Williams <peterw@ximian.com> 7/2/2001
]

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.

....
...