Files
evolution/camel
Chris Toshok aedfd03572 borrow some code from the imap provider to query the user for their
2000-10-04  Chris Toshok  <toshok@helixcode.com>

	* providers/nntp/camel-nntp-auth.c (camel_nntp_auth_authenticate):
	borrow some code from the imap provider to query the user for
	their password, and pass the user/passwd to nntp.  be extra
	paranoid and zero out the password before freeing it.

	* providers/nntp/camel-nntp-store.c (camel_nntp_store_init): add
	ALLOW_USER/ALLOW_PASSWORD/ALLOW_AUTH to the url flags.
	(nntp_store_query_auth_types_generic): return our list of
	auth_types.
	(nntp_store_query_auth_types_connected): broken, return same as in
	query_auth_types_generic.

svn path=/trunk/; revision=5716
2000-10-04 20:36:10 +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-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-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-10-02 20:14:57 +00:00
2000-10-02 20:14:57 +00:00
2000-09-07 21:00:56 +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-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.

....
...