[twsocket] MAPI read Outlook outbox count
Hi Is there a way for EasyMAPI or related components to read the Number of messages lying in the Outbox of MS Outlook? I use EasyMAPI to send email through Outlook, but need to know how many messages are in the Outbox as not to send too many per hour. The limit is imposed by my ISP that only allows a transfer rate of 200MB per hour. If more is sent, the ISP simply returns the mail as undeliverable Regards Bennie Oppermann TND Technologies CC Advanced Software Engineering -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] IcsWndControl
Hello all First of all, I would like to congratulate the ICS team for the wonderful job in creating a way to share windows handles for processing messages. I´m now extensively using this mechanism in all our application. One question though, why is the default limit of 100 messages registered per handle? I know that I can specify a different value for it but why is the default 100? What are the consequences if I increase this value to 1000 or even 1? This way I could use even less handles for the whole system, but what are the drawbacks? Thanks! Eric -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] IcsWndControl
First of all, I would like to congratulate the ICS team for the wonderful job in creating a way to share windows handles for processing messages. I´m now extensively using this mechanism in all our application. Thanks ! One question though, why is the default limit of 100 messages registered per handle? I know that I can specify a different value for it but why is the default 100? What are the consequences if I increase this value to 1000 or even 1? This way I could use even less handles for the whole system, but what are the drawbacks? There is not rule. When I wrote the code, I've done some testing to see the behavior with TWSocket. I selected 100 messages as a result of this informal testing. Actually the best number is application dependent. The more message you have, the more work is to be done by a single thread. But there could be a lot of not frequently used messages and/or a small number of messages used at a high rate. I cannot advice for a value. Check the behavior of your application... -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
