>> Agreed, so we need a FAST routine. URLEncode currently >> isn't smart enough to encode a complete URL, and it is >> slow (result := result + ..) > > Next question is how smart should such a routine act? > Should it check for a valid URL in general or shall it > just check for valid encoding? > Should it auto-complete incomplete as well as auto-correct > invalid URLs like IE? When you start thinking about this stuff > the routine in mind becomes slower and slower :(
Making URLEncode faster is probably enough for the component. Checking valid URL and autocomplete is another thing. -- [EMAIL PROTECTED] The author for 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://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
