Files
evolution/camel
Jeffrey Stedfast fa272d3dc9 Macro for making comparisons easy. (camel_ustrcasecmp): Use
2001-02-07  Jeffrey Stedfast  <fejj@ximian.com>

	* camel-search-private.c (CAMEL_SEARCH_COMPARE): Macro for making
	comparisons easy.
	(camel_ustrcasecmp): Use CAMEL_SEARCH_COMPARE and check for
	end-of-string before the utf-8 error check.
	(camel_ustrncasecmp): Same.
	(camel_search_header_match): Strip leading spaces before doing
	anything else. Also use vlen and mlen so as to not need to do 500
	strlen()'s.
	(camel_ustrcasecmp): Don't get_utf8() for the 2 strings in the
	comparison part of the loop because of short-circuit expression
	evaluation. (blame JPR if this is the wrong term!)
	(camel_ustrncasecmp): Same.

svn path=/trunk/; revision=8057
2001-02-07 21:27:11 +00:00
..
2000-06-07 23:57:18 +00:00
2001-02-05 19:55:54 +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
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-08-10 17:30:50 +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
2000-08-10 17:30:50 +00:00
2000-10-24 05:23:27 +00:00
2000-10-24 05:23:27 +00:00
2001-02-05 21:52:28 +00:00
2001-01-25 05:10:59 +00:00
2001-02-05 19:55:54 +00:00
2001-02-05 19:55:54 +00:00
2000-08-10 17:30:50 +00:00
2001-02-05 22:37:24 +00:00
2000-08-10 17:30:50 +00:00
2000-11-14 21:29:21 +00:00
2000-08-10 17:30:50 +00:00
2000-08-10 17:30:50 +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.

....
...