Here at Penn we're working on a c-client based IMAP client for a large-scale unified messaging project, which will handle voicemail for several thousand IP telephony customers.
We're debating whether to develop an IDLE interface in the c-client or just use a mail_ping() loop. The client will need to monitor everyone's mailbox in order to maintain the status of the message waiting indicator light on the VOIP telephone. While the mail_ping() loop is functionally identical to IDLE, it seems to me that the tradeoff is whether to put the resource burden on the client or the server, which may start mattering when we get into the several thousand mailbox level, depending on the scalability of the client and server architectures and the specifics of the IDLE implementation on the server. Are there any plans to implement IDLE in a future release of the c-client? If I ended up writing it myself, would you welcome the contribution? Thanks, -- Mark Sirota, Associate Director, Network Engineering and Services University of Pennsylvania, Information Systems and Computing [EMAIL PROTECTED], +1 215 573 7214 _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
