On 26-Aug-05 09:05:35 Guillaume MAISON wrote: >Maurizio Lotauro a écrit : >>> >>>i'm wondering about the utility of such properties. Why not use the >>>ContentCoding and Quality within the ContentCoding component and let the >>>HttpCli use it only when its ContentCoding property is assigned. >> >> ContentCoding is not a component and it can't be. Each HttpCli must have >> its own. You cannot share it with more than one HttpCli components.
>there's something i've missed in the explanation then :) >i was not talking about sharing a component among several HttpCli. >i was talking about, well, the same way exists a HttpClientClass for the >Web server. Except that it's transparent to the developper when using it >(just by setting a property to that or that Encoding). Do you mean the ClientClass property of THttpServer? The situation is quite different. You need a list of different decoders, and you don't know in advance how long this list could be (it depend of the kind of decoders available). [...] >i'd say that i would have used something like the TAppServer and >TServerObject in Midware. I newes see MidWare. Can you explain a little more? >In a way, not to bother woth any kind of ContentCoding if none is >"attached" to the HttpCli. and everything is set wihtin the Coding object. I'm not sure that I understood what you mean. Can you elaborate? :-) >>>my 2 cents on pattern design ;) >> All cents are welkome :-) >cents by cents we'ill get some euros ;) Of, course, and probably in 50000 years I'll be very rich ;) 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
