From: Daniel W. <d...@ni...> - 2009-01-29 12:17:19
|
Paul Lesniewski wrote: > On Mon, Jan 26, 2009 at 7:22 AM, Daniel Watts <d...@ni...> wrote: >> Dear Devs, >> >> I am pretty sure a while ago I saw someone who was talking about the >> squirrelmail imap handling layer in his own application. Presumably >> because they can then rely on a imap library that is maintained by some >> mail experts (you!). >> >> We're trying to do this ourselves but have found there is a whole bunch >> of stuff (eg in imap_general.php) that is non-imap - eg calls to >> creating error boxes and use of global language variables. >> >> These require certain other webmail related files to be required which, >> of course, is added overhead. >> >> Do you have available anything/anymethod that doesn't require these >> extra includes? Or do we just need to go through and strip out anything >> that isn't directly related to interfacing with imap? > > There is not anyone I know of using the IMAP code separately for > exactly the reason you found. Doing what you are trying to do is part > of the work needed to abstract that code so it is better suited for > use in the RPC interface, from whence any application can then make > use of it. > Ok....so fancy telling us what to do so we can do this and send the file back? Guessing two tasks: 1. Make imap*.php files a set of pure imap function files which means simply stripping out any references to anything else (eg calls to error box). Functions now just take inputs and return data or error codes. 2. Update all calling files to detect errors themselves (or whatever else) and act on them. If it is as simple as that (is it ever?) then we're willing to do part 1. Let me know. Daniel |