Files
evolution/camel
Jeffrey Stedfast d103befa6d If we are online and message flags have changed in the current folder,
2001-08-16  Jeffrey Stedfast  <fejj@ximian.com>

	* providers/imap/camel-imap-store.c (imap_keepalive): If we are
	online and message flags have changed in the current folder, sync
	the flags else do a NOOP. This fixes bug #4666. Also lock around
	the NOOP command.

	* providers/imap/camel-imap-folder.c (imap_sync_online): Don't
	ever send "STORE FLAGS.SILENT ()" since Cyrus imapd doesn't like
	this (and maybe others too?) so what we'll do instead is to send
	"STORE -FLAGS.SILENT (\Seen \Answered \Deleted \Marked)" to clear
	all the flags (since this is in essence what we want to do
	anyway).

svn path=/trunk/; revision=12136
2001-08-16 23:31:34 +00:00
..
2001-05-29 21:07:11 +00:00
2001-05-13 01:44:16 +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.

....
...