On 17-Aug-05 15:17:26 Guillaume MAISON wrote: [...]
>Hi Maurizio (and others), Hi Guillaume, >i'm sorry but i've crashed my old mail reader. :-( >Could it be possible to send back the overall design pattern used for >the content encoding extension ? It is very easy to understand if you know how Delphi handle images. To add the ability to handle, for example, the gzip encoding you must create in a separate unit a class inherited from THttpContentCoding. In the initialization section you call a registration method to tell all HttpCli components that a class able to handle gzip is available. Now to add to an application the ability to handle gzip encoding you need only to include that unit in a uses clause of one unit of you project. With this approach you are free to use or not the gzip handling depending on the project. Or even using different implementation on project basis, using the same zip library that you are already using for the specific project. As side effect you can implement the encode you want, even a custom one that maybe include some sort of encryption. Of course this will work if you are able to generate that encoding on the server side. It is like jpeg. If you want that you application will support it then simply add the JPeg unit in the uses. If you are using another library simply put in the uses the right unit. This is the principle of how it works. What we are discussing are some details, but of course we can discuss about the whole things :-) >in order for me to participate to the discussion :) Oh yes, and after that don't forget to make some test too :-) 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
