Re: [twsocket] [request] smtpprot: make X-Mailer a property

2007-02-05 Thread Francois Piette
> >> good to know but thats not the clean way. > >> and needs some additional cpu cycles on every headerline of course. > FP> The clean way to add features you need is to derive your own component from > FP> ICS component and add what you need in that derived component. I agree to do > FP> slight

Re: [twsocket] [request] smtpprot: make X-Mailer a property

2007-02-04 Thread retnyg
>> good to know but thats not the clean way. >> and needs some additional cpu cycles on every headerline of course. FP> The clean way to add features you need is to derive your own component from FP> ICS component and add what you need in that derived component. I agree to do FP> slight changes t

Re: [twsocket] [request] smtpprot: make X-Mailer a property

2007-02-04 Thread Francois PIETTE
> good to know but thats not the clean way. > and needs some additional cpu cycles on every headerline of course. The clean way to add features you need is to derive your own component from ICS component and add what you need in that derived component. I agree to do slight changes to ICS to allo

Re: [twsocket] [request] smtpprot: make X-Mailer a property

2007-02-04 Thread Arno Garrels
[EMAIL PROTECTED] wrote: > a protected variable of the object would suffice, so experienced users > could do a hack typecast to access it, if for some reason somebody > dont wont the value to be easily accessible. I don't know whether it's the author's intention to make it harder to change? A prop

Re: [twsocket] [request] smtpprot: make X-Mailer a property

2007-02-04 Thread Angus Robertson - Magenta Systems Ltd
> pls make it a property, so we dont have to mess around in ICS source > on every new release. Agreed, I remove the ICS advertisement from every new release. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Vis

Re: [twsocket] [request] smtpprot: make X-Mailer a property

2007-02-04 Thread retnyg
a protected variable of the object would suffice, so experienced users could do a hack typecast to access it, if for some reason somebody dont wont the value to be easily accessible. rgn> good to know but thats not the clean way. rgn> and needs some additional cpu cycles on every headerline of cou

Re: [twsocket] [request] smtpprot: make X-Mailer a property

2007-02-04 Thread retnyg
good to know but thats not the clean way. and needs some additional cpu cycles on every headerline of course. best regards, retnyg AG> [EMAIL PROTECTED] wrote: >> pls make it a property, so we dont have to mess around in ICS source >> on every new release. AG> There's an event OnHeaderLine. No n

Re: [twsocket] [request] smtpprot: make X-Mailer a property

2007-02-04 Thread Arno Garrels
[EMAIL PROTECTED] wrote: > pls make it a property, so we dont have to mess around in ICS source > on every new release. There's an event OnHeaderLine. No need to add a new property. procedure TMySmtp.SmtpHeaderLine(Sender: TObject; Msg: Pointer; Size: Integer); begin if StrLIComp(Msg, 'X-Ma

[twsocket] [request] smtpprot: make X-Mailer a property

2007-02-04 Thread retnyg
pls make it a property, so we dont have to mess around in ICS source on every new release. best regards, retnyg -- 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