> Francois, > Then there are situations that your previous > argument will fail: Consider an application using > HttpCli that does not automatically encode URLs in > the URL property. Users will complain that "If I > enter <address with a space> in IE it works, but your > software is broken!". If your response is "have the > developer fix his application",
Yes, indeed. The component is not a browser, it is a HTTP protocol handler. > then it is the same > as saying "have the server developer fix his > relocation code", no? It isn't. > My point is that if you want your component to > behave in the same expected ways as a browser would, I don't want that. The component is not a browser. > then the appropriate solution is to force automatic > encoding all the time, which is what browsers do. If > already encoded URLs are taken into consideration, > then it won't break any existing code. Sure it would break code. You can't make distinction between an encode URL containin a space and an unencode URL containing a percent (altough a percent sign is not common in real URL). > If you think -- like me -- that it is the > responsibility of the application developer to > properly encode URLs, and not the component, then the > solution for those applications that require the > IE-like behaviour is for the developer to call > UrlEncode himself at the application level, I agree. > and to not use FollowRedirect, but to handle redirections > himself and properly encode URLs. There I don't agree. If the component do automatic relocation, then it must take appropriate action to encode URL. > One more thing: Your concern about breaking > existing code when encoding the URL property holds > true also if you UrlEncode the redirecion URL. That > is, if the server responds with a properly encoded > URL, and you re-encode it again, you will mangle the > URL. And if you can take special care to compensate > for this, why can't it be done for all URLs? There are URL feed externaly to the component (ie: The URL property before a GET) which the developer has to encode properly, and URL handled internally by the component (automatic relocation) which the component must handle properly. > I'm sorry for dragging this on, but I just don't > understand the push for solving "the redirection" > issue as a special case. If you think we've gone > off-topic, feel free to reply by personal e-mail. No problem. I'm open to discussion. It is always interesting to share opinions (without flaming others). Altough I like to defend my opinions, I also like to have it criticized by other and to hear other's opinions. The subject is plainly on-topic ! So go ahead and keep defend you opinion ! Everyone is welcome to do the same. [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
