What RFCs need to be considered in developing an IMAP client? -

-

in theory, set of request comments (rfc) contain developer needs know build imap client. however, not easy know rfcs need considered , ones can ignored.

does have rfc roadmap steer developers through this? rfc roadmap, mean:

  • a complete list of rfcs need read , understood, in order develop imap client.
  • an indication of rfcs no longer need considered, because have been superseded.
  • a summary of relevant rfcs.
  • detail on how relevant rfcs interrelate each other.
  • an indication of logical order read , understand relevant rfcs.

the roadmap reasonably short. start imap 4rev1 rfc, rfc 3501. has normative references appendix lists rfcs directly depends on, , references rfcs in appropriate places in document.

the crucial ones -- can read them in order -- internet message format (i'd recommend rfc 5322 instead of rfc 2822 more up-to-date), mime rfcs (rfc 2045, 2046, , 2047), content-disposition (rfc 2183), tls (rfc 2595), , utf-7 (rfc 2152) handle non-ascii folder names.

once you've got baseline protocol finished, you'll want start looking @ extensions. of them make life easier... when server provides support. you'll want idle (rfc 2177) , uidplus (rfc 4315). sort (rfc 5256) 1 well, , namespace (rfc 2342) may useful. you'll need handle sasl authentication mechanisms, start rfc 1731 , go there necessary.

here's text appendix a:

the following documents contain definitions or specifications necessary understand document properly:  [abnf]                crocker, d. , p. overell, "augmented bnf                       syntax specifications: abnf", rfc 2234,                       november 1997.  [anonymous]           newman, c., "anonymous sasl mechanism", rfc                       2245, november 1997.   [charset]             freed, n. , j. postel, "iana character set                       registration procedures", rfc 2978, october                       2000.  [digest-md5]          leach, p. , c. newman, "using digest                       authentication sasl mechanism", rfc 2831,                       may 2000.  [disposition]         troost, r., dorner, s. , k. moore,                       "communicating presentation information in                       internet messages: content-disposition                       header", rfc 2183, august 1997.  [imap-tls]            newman, c., "using tls imap, pop3 ,                       acap", rfc 2595, june 1999.  [keywords]            bradner, s., "key words use in rfcs                       indicate requirement levels", bcp 14, rfc 2119,                       march 1997.  [language-tags]       alvestrand, h., "tags identification of                       languages", bcp 47, rfc 3066, january 2001.  [location]            palme, j., hopmann, a. , n. shelness, "mime                       encapsulation of aggregate documents, such                       html (mhtml)", rfc 2557, march 1999.  [md5]                 myers, j. , m. rose, "the content-md5 header                       field", rfc 1864, october 1995.  [mime-hdrs]           moore, k., "mime (multipurpose internet mail                       extensions) part three: message header                       extensions non-ascii text", rfc 2047,                       november 1996.  [mime-imb]            freed, n. , n. borenstein, "mime                       (multipurpose internet mail extensions) part                       one: format of internet message bodies", rfc                       2045, november 1996.  [mime-imt]            freed, n. , n. borenstein, "mime                       (multipurpose internet mail extensions) part                       two: media types", rfc 2046, november 1996.  [rfc-2822]            resnick, p., "internet message format", rfc                       2822, april 2001.  [sasl]                myers, j., "simple authentication , security                       layer (sasl)", rfc 2222, october 1997.  [tls]                 dierks, t. , c. allen, "the tls protocol                       version 1.0", rfc 2246, january 1999.  [utf-7]               goldsmith, d. , m. davis, "utf-7: mail-safe                       transformation format of unicode", rfc 2152,                       may 1997.  following documents describe quality-of-implementation issues should considered when implementing protocol:  [imap-implementation] leiba, b., "imap implementation                       recommendations", rfc 2683, september 1999.  [imap-multiaccess]    gahrns, m., "imap4 multi-accessed mailbox                       practice", rfc 2180, july 1997.

Comments

Post a Comment

Popular posts from this blog

javascript - Enclosure Memory Copies -

-
function myclass() { //lots , lots of vars , code here. this.bar = function() { //do numerous enclosed myclass vars } this.foo = function() { alert('hello'); //don't enclosed variables. } } each instance of myclass gets own copy of bar , foo, why prototyped methods use less memory. however, know more memory use of inner methods. it seems obvious me (1) below must true. agree? not distinct myclass instances have own distinct copies of bar, must have own distinct copies of myclass enclosure. (or else how bar method keep myclass variables straight on per instance basis?) now (2) question i'm after. since inner foo method doesn't use in myclass enclosure natural qustion is: javascript smart enough not keep myclass enclosure in memory use of foo? this depend entirely on implementation not language. naive implementations keep far more around others. answer true e.g. v8 (chrome's js engine) may not true spider...
Read more

php - Replacing tags in braces, even nested tags, with regex -

-
example preg_replace('/\{[a-za-z.,\(\)0-9]+\}/', 'replaced', 'lorem ipsum dolor sit {tag1({tag2()})}, consectetur adipiscing elit.'); the result: lorem ipsum dolor sit {tag1(replaced)}, consectetur adipiscing elit. question as can see "tag2" has been replaced, want replace "tag1" know how can this? (in cases might this: {tag1({tag2({tag3()})})}) , on.) btw using preg_replace_callback, easier show preg_replace here site can test code: http://www.spaweditor.com/scripts/regex/index.php you need add curly braces character set. here's pattern used: /\{[a-za-z.,\(\)\{\}0-9]+\}/ and here result: "lorem ipsum dolor sit replaced, consectetur adipiscing elit."
Read more