2000-11-11 Not Zed <NotZed@HelixCode.com>
* camel-mime-parser.c:
(folder_scan_content): Go until inend, not inend+1. Changed the
continuation and retry logic to be simpler and more robust. If we
can't find a marker within
the atleast we need, just set it to 1, and try again, rather than
just going to the next smaller limit (boundary check checks the
length anyway).
(header_append): streamline the empty line case. And strip
trailing \r's if there are any (\n's already stripped).
(folder_scan_header): Reordered and cleaned up a lot. Check for
continuation only once, and compress lwsp then. Assume the header
buffer already has end of line's stripped, and simplify some things:
Only check for end of headers once and easier.
Dont check to remove end of line character
Dont bother testing inptr-start if we get a boundary match - it is
always zero.
(folder_scan_header): Removed the unused part variable, and a few
pointless assignments.
(folder_scan_header): Change the end limit to be 1 higher, to make
sure we get all content.
(folder_scan_content): And here too.
(folder_scan_header): Killed a warning.
(folder_push_part): Removed a bad comment. Actually
boundarylenfinal can be zero for a new message not in a
multipart. So we fix that here.
svn path=/trunk/; revision=6542
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.
....
...
Not Zed
d99fd19df9