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). > Are you using D7? I think you are speaking of a feature of OI introduced with > that version. i'm effectively using D7... didn't know it was a feature available only since that version. > This is what will happen internally, i.e. the Options wil reflect the > properties value of ContentCodiing. > i'd say that i would have used something like the TAppServer and TServerObject in Midware. 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. >>my 2 cents on pattern design ;) > All cents are welkome :-) cents by cents we'ill get some euros ;) Best regards, -- Guillaume MAISON - [EMAIL PROTECTED] 83, Cours Victor Hugo 47000 AGEN Tél : 05 53 87 91 48 - Fax : 05 53 68 73 50 e-mail : [EMAIL PROTECTED] - Web : http://nauteus.com -- 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
