Files
evolution/camel
Jeffrey Stedfast a11414daf6 Updated to use the new API from a fe commits ago for the NSS stream. This
2003-03-03  Jeffrey Stedfast  <fejj@ximian.com>

	* camel-tcp-stream-openssl.c (camel_tcp_stream_ssl_new): Updated
	to use the new API from a fe commits ago for the NSS stream. This
	is just to make it compile, but does not update the behaviour to
	act like the NSS stream. Note that people shouldn't be using
	OpenSSL anyway.
	(camel_tcp_stream_ssl_new_raw): Same.

	* camel-process.[c,h]: New source file containing convenience
	functions for process creation/termination mainly for use with
	Pipe filters but should be usable for anything we want.

	* camel-io.[c,h]: New source files implementing read/write system
	calls with proper error checking and cancellation
	(ie. StreamFs::read/write and CamelTcpStreamRaw::read/write). No
	sense duplicating the same code over and over. Now I can use this
	same code easily in other i/o code (such as Pipe filters and gpg
	code?).

svn path=/trunk/; revision=20132
2003-03-03 22:53:15 +00:00
..
2003-02-28 21:55:06 +00:00
2002-03-25 21:47:36 +00:00
2002-03-01 21:39:17 +00:00
2002-06-14 21:33:45 +00:00
2003-02-25 19:43:22 +00:00
2003-02-25 19:43:22 +00:00
2002-03-12 20:36:08 +00:00
2002-06-14 21:33:45 +00:00
2001-10-27 16:59:46 +00:00
2003-02-25 19:43:22 +00:00
2003-02-25 19:43:22 +00:00
2003-02-28 21:55:06 +00:00
2002-11-07 21:34:17 +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
2001-10-27 16:59:46 +00:00
2001-10-27 16:59:46 +00:00
2002-07-11 22:30:51 +00:00
2002-03-01 21:39:17 +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
2003-02-25 19:43:22 +00:00
2002-03-01 21:39:17 +00:00
2003-02-25 19:43:22 +00:00
2002-11-08 06:59:12 +00:00
2003-02-25 19:43:22 +00:00
2001-10-27 16:59:46 +00:00
2003-02-27 04:53:09 +00:00
2002-06-26 18:49:05 +00:00
2003-02-05 04:53:53 +00:00
2002-10-31 21:41:26 +00:00
2002-06-26 22:15:24 +00:00
2002-06-03 02:56:35 +00:00
2002-06-03 02:56:35 +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
2001-10-27 16:59:46 +00:00
2002-05-24 20:14:59 +00:00
2001-10-27 16:59:46 +00:00
2003-02-28 21:55:06 +00:00
2003-02-28 21:55:06 +00:00
2002-07-31 01:03:10 +00:00
2002-07-31 01:03:10 +00:00
2001-10-27 16:59:46 +00:00
2003-02-14 20:44:39 +00:00
2003-02-25 19:43:22 +00:00
2002-06-03 02:56:35 +00:00
2002-03-01 21:39:17 +00:00
2003-02-26 19:40:37 +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.

....
...