> Excuse me, but how I can know that you have missed the key messages
> and don't download the file that we are speaking?
> There are a snipped of messages from Francois in this mailing list:
> Subject: [twsocket] HTTP client component and document encoding
> Date: 21 Jul 2005 17:15:19 GMT
Yes, I
On 29-Aug-05 09:11:37 Guillaume MAISON wrote:
>Maurizio Lotauro a écrit :
>> I'm not sure that I understood what you mean. Can you elaborate? :-)
>Well to make it simple :
[...]
>or, as for what happens with TBitmap, TJpeg, etc... this can be
>registered within initialization of the unit...
T
On 29-Aug-05 09:51:00 Angus Robertson - Magenta Systems Ltd wrote:
>> Huu??? No no, this is the "original" version made by Xavier. What I
>> wrote referred to my version.
>>
>> I just sent a release candidate to Francois, wait his announcement.
>It was the latest version available from the ICS we
> I just sent a release candidate to Francois, wait his announcement.
Done.
See my other message.
--
[EMAIL PROTECTED]
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
> Huu??? No no, this is the "original" version made by Xavier. What I
> wrote referred to my version.
>
> I just sent a release candidate to Francois, wait his announcement.
It was the latest version available from the ICS web site. If GZIP did
not work in that version, why was it posted atall?
Maurizio Lotauro a écrit :
>
> 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
On 28-Aug-05 20:07:00 Angus Robertson - Magenta Systems Ltd wrote:
>> a) use the new httpcli to verify if it still "works" as before, i.e.
>it
>> doesn't break your code (no gzip nor dll involved)
>The 5 June version does seem to be backward compatible, without
>{$DEFINE Xlb_GzHttp}.
Huu??? No n
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.
>>
>>
> a) use the new httpcli to verify if it still "works" as before, i.e.
it
> doesn't break your code (no gzip nor dll involved)
The 5 June version does seem to be backward compatible, without
{$DEFINE Xlb_GzHttp}.
> b) test it with your gzip implementation if you made it in a inherited
> comp
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.
On 24-Aug-05 19:28:11 Francois PIETTE wrote:
[...]
>I think this behaviour is the normal expected behaviour of the way
>inheritance work.
Yes and no. The feedback using the OI is that you change a single
property value, but effectly you change the value of a single bit.
[..]
>> In either case
On 24-Aug-05 22:13:53 Gunnar wrote:
>> The problem is that a set is practically a single value.
>That's not a problem!
Yes it is when you use the VFI.
>> Take for example the
>> TFont.Style property. If you set the bold in an inherited form then in the
>> dfm you will see Font.Style = [fsBold]
Scrive Guillaume MAISON <[EMAIL PROTECTED]>:
> Francois PIETTE a écrit :
[...]
> > I want that the two new properties be added to the Options property.
> > Names: httpoEnableContentCoding and httpoUseQuality
>
> i'm wondering about the utility of such properties. Why not use the
> ContentCodin
Francois PIETTE a écrit :
>>in the base form but it must do the same for each inherited form that has
>>changed the Options property.
>>While this could be accepted for related switches like TFont.Style I don't
>>think that it is acceptable when they are unrelated.
>
>
> I think this behaviour is
> The problem is that a set is practically a single value.
That's not a problem!
> Take for example the
> TFont.Style property. If you set the bold in an inherited form then in the
> dfm
> you will see Font.Style = [fsBold]. Now if in the base form you want that the
> font has the italic sty
>> Anyway, I'm not aware of any problem with sets and VFI.
>> You could explain that.
> The problem is that a set is practically a single value. Take for example
> the
> TFont.Style property. If you set the bold in an inherited form then in the
> dfm
> you will see Font.Style = [fsBold]. Now if
Scrive Angus Robertson - Magenta Systems Ltd <[EMAIL PROTECTED]>:
> > So you get it. Can you keep it and read when you have better time?
>
> I've already said I will try to test your HTTP component when I have
> the time, but that I will not use anything with a DLL, which is what
> the zip I do
Scrive Francois Piette <[EMAIL PROTECTED]>:
> > Anyway, I would like to close this enhancement. What I absolute need
> > is to decide about how add the new parameters.
> > I spoke about the problemd with sets and VFI, i.e. Visual Form
> > Inheritance. Should I explain what kind of problem is?
> >
> So you get it. Can you keep it and read when you have better time?
I've already said I will try to test your HTTP component when I have
the time, but that I will not use anything with a DLL, which is what
the zip I downloaded seems to contain. So it seems I have to do extra
work implementing
> Anyway, I would like to close this enhancement. What I absolute need
> is to decide about how add the new parameters.
> I spoke about the problemd with sets and VFI, i.e. Visual Form
> Inheritance. Should I explain what kind of problem is?
> Do you know how VFI works?
I know how VFI works and I
On 23-Aug-05 19:39:00 Angus Robertson - Magenta Systems Ltd wrote:
>> About recent discussion of HttpCli changes, I made a reply (on topic)
>> to three people: Angus, Guillaume and Francois.
>> I received my posts and see they in the archive of elists, but I never
>> get a reply and none are prese
On 23-Aug-05 19:54:50 Francois PIETTE wrote:
>I haven't noticed any problem with the list.
>I have noticed that it is very difficult to have people actively
>participating in development :-((
>Unfortunately, most people here are interested in using ICS but not
>developping it. Sometimes it is easi
nt: Tuesday, August 23, 2005 8:08 PM
Subject: [twsocket] How reliable is this mailing list?
> About recent discussion of HttpCli changes, I made a reply (on topic) to
> three
> people: Angus, Guillaume and Francois.
> I received my posts and see they in the archive of elists, but I n
> About recent discussion of HttpCli changes, I made a reply (on topic)
> to three people: Angus, Guillaume and Francois.
> I received my posts and see they in the archive of elists, but I never
> get a reply and none are present in the archive.
> Is it a problem of the ML or all want drop the di
About recent discussion of HttpCli changes, I made a reply (on topic) to three
people: Angus, Guillaume and Francois.
I received my posts and see they in the archive of elists, but I never get a
reply and none are present in the archive.
Is it a problem of the ML or all want drop the discussion?
25 matches
Mail list logo
