On 16-Aug-05 16:30:00 Angus Robertson - Magenta Systems Ltd wrote: >> 1. Your choice. You have now the opportunity to be sure the new >> version doesn't break existing code, specially yours.
>No, it's the job of the person introducing the changes to make sure the >component is backward compatible, and if not, document VERY CLEARLY at >the top of the code any implications of the changes, not just in this >mailing list. And to clearly mark and date and changes. The problem that you mention was not a compability issue but a bug. >I, nor anyone else, don't the time or inclination to compare every new >source for undocumented changes, and try to work out what has been done. >> 2. Nevertheless it is good to have it supported by the component in an >> extensible way. We are not only talking about gzip but any >> compression scheme. >So what other compression schemes are used by common HTTP servers? RFC mention gzip, compress and deflate. IE send gzip and deflate. In any case the discussion is generic, the changes made will open the component on every encoding you want, even a custom one. Bye, Maurizio. -- 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
