Hello, We use TStringList quicksort/binary search routine I wrote for caching--works so well that I can recommend.
Also, has anybody tested the IPv6 with listening/server components? Best Regards, SZ On Wed, Jun 2, 2010 at 10:04 PM, Francois PIETTE <francois.pie...@skynet.be>wrote: > How fast/slow this implementation works with thousands of >> concurrent requests is of course untested. One DNS lookup may >> take one or even multiple seconds in the worst case. >> > > Shouldn't TWSocket have his own internal cache for DNS lookup ? Or maybe > instead of more complex TWSocket, maybe a component dedicated to DNS lookup > could have it. As simple strategy inside TWSocket would then be enough for > most applications while high load applications could benefit from a caching > component. This is also, imo, good design to offload a specific task to a > specific class. > > Of course this could be done in each application. > > AVL tree used in SSL is a good candidate to build a cache system. > > > -- > francois.pie...@overbyte.be > 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 > -- 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
