Files
evolution/camel
Jeffrey Stedfast 2003a69501 Don't free 'resp' as it doesn't point to the beginning of the allocated
2000-10-16  Jeffrey Stedfast  <fejj@helixcode.com>

	* providers/imap/camel-imap-command.c
	(camel_imap_response_extract): Don't free 'resp' as it doesn't
	point to the beginning of the allocated data, instead free
	response->untagged->pdata[i]. Also, if '*resp' is equal to a space
	character, then set resp = imap_next_word (resp) rather than
	expecting resp++ to work (there's a list broken IMAP daemons that
	like to put extra spaces between tokens).
	(imap_read_response): Don't expect 'respbuf+2' to be where the
	untagged number response to start (see above fix for an
	explanation).

svn path=/trunk/; revision=5960
2000-10-17 02:38:18 +00:00
..
2000-06-07 23:57:18 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-11 02:57:11 +00:00
2000-08-10 17:30:50 +00:00
2000-08-11 02:57:11 +00:00
2000-08-11 02:57:11 +00:00
2000-08-10 17:30:50 +00:00
2000-08-25 04:31:13 +00:00
2000-08-11 02:57:11 +00:00
2000-08-11 02:57:11 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-16 18:33:20 +00:00
2000-08-10 17:30:50 +00:00
2000-06-22 21:51:40 +00:00
2000-10-02 20:14:57 +00:00
2000-10-02 20:14:57 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-11 02:57:11 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +00:00
2000-05-29 11:09:32 +00:00
2000-09-28 11:31: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.

....
...