commit: incubator/Imap_Client/lib/Horde/Imap Client.php incubator/Imap_Client/lib/Horde/Imap/Client Base.php Cclient.php Socket.php

"Michael M Slusarz" <[email protected]>
Newsgroups gmane.comp.horde.cvs
Message-ID <[email protected]>
slusarz     2008-10-02 01:33:24 EDT

  Modified files:
    Imap_Client/lib/Horde/Imap Client.php 
    Imap_Client/lib/Horde/Imap/Client Base.php Cclient.php 
                                      Socket.php 
  Log:
  Tada!  This should be it - all of RFC 3501 should now be implemented in the
  Socket driver (and 99% in the Cclient driver with the last remaining item -
  envelope data for message/rfc822 parts in the structure information - most
  likely not doable in c-client).  No guarantees on these latest BODY fetches
  as they haven't been tested much.  But the initial API should now be complete.
  
  And check out that fetch() documentation - 274 lines of doc for that one
  function!  That's got to be some kind of record.  (But the IMAP 'BODY' command
  is by far the single most complicated API grammar I have ever encountered so
  the effort needed to abstract out the functionality is necessarily complex.)
  
  Revision  Changes    Path
  1.19      +11 -6     incubator/Imap_Client/lib/Horde/Imap/Client.php
  1.33      +214 -88   incubator/Imap_Client/lib/Horde/Imap/Client/Base.php
  1.31      +96 -9     incubator/Imap_Client/lib/Horde/Imap/Client/Cclient.php
  1.38      +130 -10   incubator/Imap_Client/lib/Horde/Imap/Client/Socket.php

  Chora Links:
  http://cvs.horde.org/diff.php/incubator/Imap_Client/lib/Horde/Imap/Client.php?r1=1.18&r2=1.19&ty=u
  http://cvs.horde.org/diff.php/incubator/Imap_Client/lib/Horde/Imap/Client/Base.php?r1=1.32&r2=1.33&ty=u
  http://cvs.horde.org/diff.php/incubator/Imap_Client/lib/Horde/Imap/Client/Cclient.php?r1=1.30&r2=1.31&ty=u
  http://cvs.horde.org/diff.php/incubator/Imap_Client/lib/Horde/Imap/Client/Socket.php?r1=1.37&r2=1.38&ty=u

--
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.