>Callbacks I can understand but the constant copying and duplicating   
 >and transfering of data around the sieve context... eh.. what for?   
   
 I think it may have had something to do with the fact that libsieve did 
not originate as a standalone library.  It began as the Sieve code from 
Cyrus IMAP, until Aaron ripped it out and made a standalone library out of 
it.  I'm sure that had a profound effect on the nature of the API.  
   
 All things considered, he did a good job.  The Sieve processor for 
Citadel came together without a lot of difficulty thanks to libsieve.  
  

Reply via email to