Hastymail DEVELOPMENT file

This file is for some notes regarding the coding
guidelines used in Hastymail and the RFC references.

Basic guidelines for hastymail development:

1.  Use UID instead of message sequence number ALWAYS
2.  No frames, no javascript, no cookies.
3.  If you can make the code faster do so, even if it is uglier :)
4.  Stay RFC compliant, but work with broken servers if possible
5.  Don't bog the user down with options, keep it simple
6.  Keep html generation and backend code as separate as possible
7.  Use CSS for style and theme aspects
8.  Indent 4 spaces, NO tabs
9.  No alternate PHP syntax stuff
10. Code for PHP 4.1+
11. Keep the HTML output valid by the W3C HTML 4.01 Transitional standard

RFC's used for hastymail development:

IMAP RFC 3501           http://www.faqs.org/rfcs/rfc3501.html
IMAP SORT EXTENSION     http://www.ietf.org/internet-drafts/draft-ietf-imapext-sort-10.txt
IMAP THREAD EXTENSION   http://www.ietf.org/internet-drafts/draft-ietf-imapext-thread-12.txt
SMTP RFC 821            http://www.faqs.org/rfcs/rfc821.html
MIME RFC 2045-2049      http://www.nacs.uci.edu/indiv/ehood/MIME/MIME.html
MESSAGE RFC 2822        http://www.faqs.org/rfcs/rfc2822.html
HTTP 1.1 RFC 2068       http://www.w3.org/Protocols/rfc2068/rfc2068
