Author |
|
NobodyFamous Newbie
Joined: 19 October 2007 Location: Canada
Online Status: Offline Posts: 11
|
Posted: 12 November 2009 at 12:51pm | IP Logged
|
|
|
Hi,
I have a somewhat unique circumstance in that I'm designing a server to maintain connections on behalf of mobile clients to another server for long periods of time.
Basically I'm developing a server application that will maintain an imap connection for each mobile client, so rather than my server accepting incoming connections, it's creating outgoing connections.
I'm wondering how MailBee's IMAP.NET will scale in this situation. For instance, I don't see any way to tell the Imap object to bind to a specific network interface, and I am not sure if you're setting properties on the socket like the ReuseAddress SocketOption, or the ExclusiveAddressUse property.
As I understand it, Windows Server 2003 should be able to handle more than 65k connections if I have multiple network interfaces that can all reach the destination.
Please advise!
|
Back to Top |
|
|
Alex AfterLogic Support
Joined: 19 November 2003
Online Status: Offline Posts: 2206
|
Posted: 13 November 2009 at 12:40pm | IP Logged
|
|
|
We'll be adding a feature to specify your own socket settings soon. Next week, I suppose.
If you open a ticket in our helpdesk system, you'll be prompted about the update.
Regards,
Alex
|
Back to Top |
|
|
Alex AfterLogic Support
Joined: 19 November 2003
Online Status: Offline Posts: 2206
|
Posted: 20 November 2009 at 9:38am | IP Logged
|
|
|
The latest version of standalone MailBee.NET.dll adds a new overload of Imap.Connect method which let you use local end points, socket parameters, etc.
The latest beta version of MailBee.NET.dll is available at:
http://www.afterlogic.com/updates/mailbee_net_1.zip (.NET 1.1 and above)
http://www.afterlogic.com/updates/mailbee_net_2.zip (.NET 2.0 and above)
Regards,
Alex
|
Back to Top |
|
|