Re: [twsocket] Installing ICS under windows 3.11
> Thank you for your very prompt reply to my query. My problem is not with > delphi, but I cannot even unpack the .zip file as files in the DotNet > directory have long filenames and filenames with multiple extensions. Trying > to unzip and setup the directory structures causes multiple error messages > from winzip, so I don't get as far as trying to install the components in > delphi. Just unzip the zip file on a modern computer with winzip which handle long filenames, then copy the needed files to your other computer (you can rezip unzing a old pkzip which will use 8.3 file names). No file with long filenames are required for Delphi 1. The files with long filenames are for dotnet only. > PS, I live on Russell Island in Australia. I will send a postcard of > Brisbane which is the nearest city. It is even better a postcard from Russell Island. > Thank you for creating this suite of > components and offering them as freeware. You're welcome. -- [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://www.overbyte.be
Re: [twsocket] HttpCli: Opinion wanted !
> How do you think that all we heavily tested for weeks if nobody, > except the developer(s), made any test? I only have a single development environment, and I need to be able to produce bug fix versions of several applications at short notice, often hours, that get widely distributed within hours. Many other professional developers are probably in exactly the same situation. So using new versions of components is very delicate, thus the absolute need for backward compatibly and full version and change documentation, to allow the risk of new versions to be accessed. I do keep up to date with official ICS betas, including SSL, test them for weeks or months in various live applications, report problems, and often try to fix them myself, for the benefit of other uses, but only if I can see the risk of doing so and I can be sure the changes will not cause me major grief. > We are not speaking specific on gzip but on handlig encoding in a > generic way. Not really fussed how many different fancy schemes are supported. > If you are using VCLZip library to handle gzip content then it could > be interesting to see if you are able to add it to this "new" version > or if it is missing something indispensable. Vclzip is commercial, I used it to replace the previous Borland Zlib implementation because it was convenient, but I'd rather use open source for anything new. I will test your changed component in one of my applications provided, provided there is no DLL requirement. I'm also going to try to add ZLIB compression to the FTP client and server, at the same time as adding 64-bit stream support and removing support for long obsolete compilers. Angus -- 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
Re: [twsocket] HttpCli: Opinion wanted !
> I'm also going to try to add
> ZLIB compression to the FTP client and server, at the same time as
> adding 64-bit stream support and removing support for long obsolete
> compilers.
Don't go too fast to remove existing code because then it will be very
difficult to merge your
changes and those from others including me. Risks are that you either have to
reimplement your
changes in the next version or that you take a one way ticket to your own
version diverging from the
official one.
It is much better you add your changes and let existing code as it is. I
understand you don't want
to support older compiler. OK, but don't remove existing code. You can surrond
your changes with
something like {IFDEF COMPILER7_UP}/{$ENDIF} like it is done for NTLM support.
One day, I will take the current release and remove support for anything below
Delphi 7 and insert
the new stuff that I already developped but not published that allow to use a
huge number of
concurrent sockets by drastically reducing the number of message queues.
--
[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://www.overbyte.be
[twsocket] TWSocket DNSLookup
Hello Francois,
Strange after all these years I did not check the AHostName before
calling DNSLookup for the first time :)
Anyway there is something I wonder. First exception is raised, then
TriggerDnsLookupDone is called with the right argument, however because
the exception it is never called, and it should be with or without
error.
Assign something on the OnError is not the way to go. Should the
RaiseException line not be commented out ? What do you think ?
procedure TCustomWSocket.DnsLookup(const AHostName : String);
var
IPAddr : TInAddr;
HostName : String;
begin
if AHostName = '' then begin
RaiseException('DNS lookup: invalid host name.'); // comment ?
TriggerDnsLookupDone(WSAEINVAL);
Exit;
end;
--
Rgds, Wilfried
http://www.mestdagh.biz
--
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
Re: [twsocket] HttpCli: Opinion wanted !
> Don't go too fast to remove existing code because then it will be very > difficult to merge your > changes and those from others including me. Risks are that you either > have to reimplement your > changes in the next version or that you take a one way ticket to your > own version diverging from the official one. You personally agreed a year ago that the current released version of ICS would be last to continue support for long obsoleted compilers. Despite several requests, you have never given a reason why the few developers that are prepared to contribute free time to enhance your components should be massively handicapped by the necessity to write conditional code that continues to allow Delphi 1 to 3 to be used, while being unable to use any Delphi language features added since Delphi 3. Who are these people that actually need to use new versions of ICS on Delphi 1 to 3? Why can not they stay on old reliable versions? Do they actually want new features? Unless there are positive answers to these questions, or a major consensus from this mailing list that Delphi 1 to 3 support is actually important for ICS, I don't believe anyone should be forced to waste time writing and testing new conditional code. I simply don't have Delphi 1 to 3 installed, so can not test such conditional code. Angus -- 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
Re: [twsocket] TWSocket DNSLookup
> Assign something on the OnError is not the way to go. Should the
> RaiseException line not be commented out ? What do you think ?
The code is OK for both those using OnError and those using exception handling,
IMO.
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Wilfried Mestdagh" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, August 17, 2005 11:57 AM
Subject: [twsocket] TWSocket DNSLookup
> Hello Francois,
>
> Strange after all these years I did not check the AHostName before
> calling DNSLookup for the first time :)
>
> Anyway there is something I wonder. First exception is raised, then
> TriggerDnsLookupDone is called with the right argument, however because
> the exception it is never called, and it should be with or without
> error.
>
> Assign something on the OnError is not the way to go. Should the
> RaiseException line not be commented out ? What do you think ?
>
> procedure TCustomWSocket.DnsLookup(const AHostName : String);
> var
> IPAddr : TInAddr;
> HostName : String;
> begin
> if AHostName = '' then begin
> RaiseException('DNS lookup: invalid host name.'); // comment ?
> TriggerDnsLookupDone(WSAEINVAL);
> Exit;
> end;
>
> --
> Rgds, Wilfried
> http://www.mestdagh.biz
>
> --
> 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
--
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
Re: [twsocket] HttpCli: Opinion wanted !
> > Don't go too fast to remove existing code because then > > it will be very difficult to merge your > > changes and those from others including me. Risks are > > that you either have to reimplement your > > changes in the next version or that you take a one way > > ticket to your own version diverging from the official one. > > You personally agreed a year ago that the current released version of > ICS would be last to continue support for long obsoleted compilers. Yes, and this is what I stated again in my previous message. > Despite several requests, you have never given a reason why the few > developers that are prepared to contribute free time to enhance your > components should be massively handicapped by the necessity to write > conditional code that continues to allow Delphi 1 to 3 to be used, > while being unable to use any Delphi language features added since > Delphi 3. In my previous message I was trying to tell you don't have to bother making new code compatible with old compiler. I was trying to say to not remove existing code. > Who are these people that actually need to use new versions of ICS on > Delphi 1 to 3? Why can not they stay on old reliable versions? Do > they actually want new features? No need to support new features for old compilers as long as those features are conditionnaly compiled. Do not break existing features, even for old compilers. > Unless there are positive answers to these questions, or a major > consensus from this mailing list that Delphi 1 to 3 support is actually > important for ICS, I don't believe anyone should be forced to waste > time writing and testing new conditional code. I simply don't have > Delphi 1 to 3 installed, so can not test such conditional code. Again, do not bother testing your code with old compiler, but add conditional compile so that your code is used only with recent compilers (D5 is enough, even D7) and do not break existing code. Please re-read carefully my previous message, keeping in mind that english is not my language and my words are not always the best to say what I want to say. -- [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://www.overbyte.be
Re: [twsocket] HttpCli: Opinion wanted !
>> You personally agreed a year ago that the current released version of >> ICS would be last to continue support for long obsoleted compilers. > Yes, and this is what I stated again in my previous message. >> Who are these people that actually need to use new versions of ICS on >> Delphi 1 to 3? Why can not they stay on old reliable versions? Do >> they actually want new features? > Do not break existing features, even for old compilers. So if you don't want to support obsolete compilers, why if it necessary to make the code compatible with obsolete compilers? This is a contradition. Sorry, but you continue to evade the real question here, why continue to support obsolete compiler with new versions of ICS? I've just done a little research of 64-bit streams, and it seems Delphi 6 was the first to support these, and I'm aware many people still use Delphi 5 so I will make that particular feature conditional. Angus -- 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
Re: [twsocket] HttpCli: Opinion wanted !
> So if you don't want to support obsolete compilers, why if it necessary > to make the code compatible with obsolete compilers? This is a > contradition. No because there is only one distribution and one source code set. > Sorry, but you continue to evade the real question here, why continue > to support obsolete compiler with new versions of ICS? Because there are still a lot of people using old compilers, frequently to maintain existing applications but also to develop new ones, even with Delphi 1 which is used for embedded systems using Win 3.x !! The price to support old compilers is cheap. Just look how many conditional compile are in the current sources: not so much. > I've just done a little research of 64-bit streams, and it seems Delphi > 6 was the first to support these, and I'm aware many people still use > Delphi 5 so I will make that particular feature conditional. OK. -- [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://www.overbyte.be
Re: [twsocket] HttpCli: Opinion wanted !
> Because there are still a lot of people using old compilers, > frequently to maintain existing > applications but also to develop new ones, even with Delphi 1 which is > used for embedded systems using Win 3.x !! OK, can all those in this list using Delphi compilers earlier than Delphi 5, Delphi 1 in particular, please respond to this message and indicate why you want to continue using a six to 10 year old compiler with the latest bugs and features for ICS? I'm really referring to professional developers here, not hobiests who may be unable to afford a new version. If there are fewer than say a dozen positive responses, I'd suggest we finally accept this argument for complicating and stalling development of ICS by supporting obsolete compilers is finally put to rest. We can not stay stuck in past, we need to look to the future. Angus -- 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
Re: [twsocket] HttpCli: Opinion wanted !
> OK, can all those in this list using Delphi compilers earlier than > Delphi 5, Delphi 1 in particular, please respond to this message and > indicate why you want to continue using a six to 10 year old compiler > with the latest bugs and features for ICS? That's not the issue. And you will not have many replies since most of ICS users don't even read this mailing list. Anyway, search for the message with subject "Re: [twsocket] Installing ICS under windows 3.11" posted earlier today and you have one recent user still using Delphi 1. -- [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://www.overbyte.be
Re: [twsocket] HttpCli: Opinion wanted !
This time I second Agnus. No professional coder would use a compiler from last decade and if an amateur wants to do so, he/she should be happy with an old ICS release version. There needs to be a time that we look further into the future and leave the past in the past. Othwerwise we would be stuck in the past. Best Regards, SubZ - Original Message - From: "Angus Robertson - Magenta Systems Ltd" <[EMAIL PROTECTED]> To: Sent: Wednesday, August 17, 2005 4:00 PM Subject: Re: [twsocket] HttpCli: Opinion wanted ! >> Because there are still a lot of people using old compilers, >> frequently to maintain existing >> applications but also to develop new ones, even with Delphi 1 which is >> used for embedded systems using Win 3.x !! > > OK, can all those in this list using Delphi compilers earlier than > Delphi 5, Delphi 1 in particular, please respond to this message and > indicate why you want to continue using a six to 10 year old compiler > with the latest bugs and features for ICS? > > I'm really referring to professional developers here, not hobiests who > may be unable to afford a new version. > > If there are fewer than say a dozen positive responses, I'd suggest we > finally accept this argument for complicating and stalling development > of ICS by supporting obsolete compilers is finally put to rest. > > We can not stay stuck in past, we need to look to the future. > > Angus > > -- > 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 -- 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
[twsocket] R: HttpCli: Opinion wanted !
I have to agree, I will like to see a .Net version soon also for the Midware :) Paolo L. Message scanned by Norton AntiVirus 2005 -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Fastream Technologies Inviato: mercoledì 17 agosto 2005 15.06 A: ICS support mailing Oggetto: Re: [twsocket] HttpCli: Opinion wanted ! This time I second Agnus. No professional coder would use a compiler from last decade and if an amateur wants to do so, he/she should be happy with an old ICS release version. There needs to be a time that we look further into the future and leave the past in the past. Othwerwise we would be stuck in the past. Best Regards, SubZ - Original Message - From: "Angus Robertson - Magenta Systems Ltd" <[EMAIL PROTECTED]> To: Sent: Wednesday, August 17, 2005 4:00 PM Subject: Re: [twsocket] HttpCli: Opinion wanted ! >> Because there are still a lot of people using old compilers, >> frequently to maintain existing >> applications but also to develop new ones, even with Delphi 1 which is >> used for embedded systems using Win 3.x !! > > OK, can all those in this list using Delphi compilers earlier than > Delphi 5, Delphi 1 in particular, please respond to this message and > indicate why you want to continue using a six to 10 year old compiler > with the latest bugs and features for ICS? > > I'm really referring to professional developers here, not hobiests who > may be unable to afford a new version. > > If there are fewer than say a dozen positive responses, I'd suggest we > finally accept this argument for complicating and stalling development > of ICS by supporting obsolete compilers is finally put to rest. > > We can not stay stuck in past, we need to look to the future. > > Angus > > -- > 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 -- 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 -- 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
[twsocket] component question
hi i canged the file variabls and operations on ftpcli to int64 and it looks like it works :-) the only problem left is that if i klick on the onprogress event it makes me a sourcecode that contains a integer instead of a int64. where can i change that ? ty roland -- 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
Re: [twsocket] [FTPCli] - Quote Method
- Original Message - From: "Artem Antonov" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Tuesday, August 16, 2005 8:48 AM Subject: [twsocket] [FTPCli] - Quote Method > Hello! > > I want to set file attributes on FTP server and use such commands: > > FtpClient.HostDirName := '/my_dir/'; > ExecuteCmd(FtpClient.Cwd, FtpClient.CwdAsync); > > FtpClient.HostFileName := 'test.txt'; > FtpClient.LocalFileName := 'chmod 644 test.txt'; > ExecuteCmd(FtpClient.Quote, FtpClient.QuoteAsync); > > But from FTP server I get: > > 16.08.2005 10:36:17 - Executing requested command... >> chmod 644 test.txt > < 500 'CHMOD': command not understood. > Request 33 done > Status code = 500. > > How I can set file attributes or where is I am wrong? > > Thanks! > > Best regards, > Artem Antonov. Try SITE CHMOD. There's no guarantee it will work though. Dan -- 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
Re: [twsocket] R: HttpCli: Opinion wanted !
This is a useless discussion. Of course we will have almost every one using D7 or D2005 say he don't need another compiler. They don't care about the other users. I do care. That made the strength of ICS for years. I don't want to discuss that anymore because it's just polemic. I already lost too much time with that. The opinion I want to hear is about the design decisions that need to be done about the HTTP client component supporting compression. See Maurizio messages and answer to the technical questions he ask. -- [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://www.overbyte.be
Re: [twsocket] component question
> i canged the file variabls and operations on ftpcli to int64
> and it looks like it works :-)
> the only problem left is that if i klick on the onprogress
> event it makes me a sourcecode that contains a integer
> instead of a int64. where can i change that ?
You have to change TFtpProgress data type to use an int64. Don't forget to
rebuild the package and
reinstall it so that delphi use the correct version.
btw: How have you changed to int64 ?
You should have replaced all integer or LongInt by a new custom type which is
conditionnaly defined.
Similar to this:
{$IFDEF COMPILER6_UP}
{$DEFINE Use64BitFiles}
{$ENDIF}
{$IFDEF Use64BitFiles}
FtpInteger = int64;
{$ELSE}
FtpInteger = integer;
{$ENDIF}
and later in the code use FtpInteger where 64 bit is desirable.
Doing so make the code compatible with older compiler version.
You can easily to a search and replace of your int64 by FtpInteger.
--
[EMAIL PROTECTED]
Author of ICS (Internet Component Suite, freeware)
Author of MidWare (Multi-tier framework, freeware)
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://www.overbyte.be
Re: [twsocket] HttpCli: Opinion wanted !
Fastream Technologies a écrit : > This time I second Agnus. No professional coder would use a compiler from > last decade and if an amateur wants to do so, he/she should be happy with an > old ICS release version. > > There needs to be a time that we look further into the future and leave the > past in the past. Othwerwise we would be stuck in the past. > > Best Regards, > > SubZ Well... it's not that simple... i've been working for french mobile phone provider. They have some applications - heavy ones as it mixes helpdesk, commercial stuff, etc... - developped with delphi 5. Having a look at how they manage their project, the quality checks that are made, the time taken for any process involving an application evolution, that may take quite a lot of time. Moreover, migrating such an application would cost *a lot* of money in : - quality checks for the new compiler version ; - adapting applications to work with a new compiler version (there're millions lines of code, even in delphi) ; - if there're 3rd party components used, you have to be sure that those components work with the new compiler version, which is *never* guaranteed ; - checking the new compiled version of the application ; - deploying the new application on more than 1000 workstations ; - checking every bug, etc... Those applications i'm talking about are part of the company backbone. So when you think about the cost of migrating an application, when you think that the first goal of such companies is making money spending it lessly possible, adding a feature using TCP/IP component is less expensive using the same compiler - which has passed all the quality checks - than the one used for the application. that's why many companies are still using old versions of delphi. You both are quite talking in a developper way, in a technical way - no offense here ;). My talking is much more as a company manager which has to take in account every cost. Developping an application - and most of all anticipating its evolutions - is a loadbalancing between technical stuff and financial stuff. ICS, whatever its version, is a simple - hence robust - Winsock API. it may surely be found in many - unknown to us - company information systems backbone. So if there're modifications - bug correction for example - you have to be sure that the new version will still be backward compatible for what already exists. I don't mean the new functionnalities, but at least the actual ones. So yes, actually, some professional developpers still use old compilers and may need the components to still work, even with a new version. IMHO, 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
Re: [twsocket] HttpCli content encoding
Maurizio Lotauro a écrit : > I repost some points to discuss: > > a) Exception in THttpContentCoding.GetCoding method [...] > > b) New properties. [...] > c) The THttpContCodHandler.Prepare return false if there is an encode > that it is unable to decompress. Actually the HttpCli doesn't check > the result, and in this case the body will be not decompressed at > all. Is it acceptable or should this situation be handled differently? [...] > d) There are two coding atomatically added: "Identity" (quality=0.5) > and "*" (quality=0). Actually they are enabled by default, should > they must disabled? > Is it ok the default value of quality? [...] Hi Maurizio (and others), 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 ? in order for me to participate to the discussion :) thanks in advance, 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
Re: [twsocket] HttpCli: Opinion wanted !
I do not want to trigger more reactions, there is probably not point, I just want to vent my position on this. I second Guillaume and Francois 100%. There has to be support for "older systems" whether we like it or not, Guillaume makes a valid point. In reality there are probably more professionals using older compilers than hobbiests who tend to go for the newer versions (affordable or not, don't think that the gross of hobbiests use "purchased" versions). PS. I still use Borland C++ Builder 5 (and still happy with it, PS. I will never go for .NET, I'll retire before I "have" to, and go live under a rock if I can't afford it, but that's a personal thing) It's the same principle like many of us still have to make sure that our software runs on early Win95 and NT4 systems, we would like to move away from it, but commercial software cannot always afford to do that (depends on what it does and who it is for). And last but definitly not least, It's Francois' pet project, his baby, his hobby, let HIM decide what to do please ! Best Regards, Peter --- Peter Van Hove CD and DVD Data recovery [EMAIL PROTECTED] www.Smart-Projects.net www.IsoBuster.com --- - Original Message - From: "Guillaume MAISON" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Wednesday, August 17, 2005 4:04 PM Subject: Re: [twsocket] HttpCli: Opinion wanted ! Fastream Technologies a écrit : > This time I second Agnus. No professional coder would use a compiler from > last decade and if an amateur wants to do so, he/she should be happy with > an > old ICS release version. > > There needs to be a time that we look further into the future and leave > the > past in the past. Othwerwise we would be stuck in the past. > > Best Regards, > > SubZ Well... it's not that simple... i've been working for french mobile phone provider. They have some applications - heavy ones as it mixes helpdesk, commercial stuff, etc... - developped with delphi 5. Having a look at how they manage their project, the quality checks that are made, the time taken for any process involving an application evolution, that may take quite a lot of time. Moreover, migrating such an application would cost *a lot* of money in : - quality checks for the new compiler version ; - adapting applications to work with a new compiler version (there're millions lines of code, even in delphi) ; - if there're 3rd party components used, you have to be sure that those components work with the new compiler version, which is *never* guaranteed ; - checking the new compiled version of the application ; - deploying the new application on more than 1000 workstations ; - checking every bug, etc... Those applications i'm talking about are part of the company backbone. So when you think about the cost of migrating an application, when you think that the first goal of such companies is making money spending it lessly possible, adding a feature using TCP/IP component is less expensive using the same compiler - which has passed all the quality checks - than the one used for the application. that's why many companies are still using old versions of delphi. You both are quite talking in a developper way, in a technical way - no offense here ;). My talking is much more as a company manager which has to take in account every cost. Developping an application - and most of all anticipating its evolutions - is a loadbalancing between technical stuff and financial stuff. ICS, whatever its version, is a simple - hence robust - Winsock API. it may surely be found in many - unknown to us - company information systems backbone. So if there're modifications - bug correction for example - you have to be sure that the new version will still be backward compatible for what already exists. I don't mean the new functionnalities, but at least the actual ones. So yes, actually, some professional developpers still use old compilers and may need the components to still work, even with a new version. IMHO, 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 -- 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
Re: [twsocket] HttpCli: Opinion wanted !
I understand your concerns but you should keep in mind that all companies in the software world at some point cuts support to old code. For example Microsoft no longer supports Win3.1 and even Win95. They surely know there are customers using these platforms but "the road ahead" is simply "business at the speed of thought"! Thanks, SZ - Original Message - From: "Guillaume MAISON" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Wednesday, August 17, 2005 5:04 PM Subject: Re: [twsocket] HttpCli: Opinion wanted ! Fastream Technologies a écrit : > This time I second Agnus. No professional coder would use a compiler from > last decade and if an amateur wants to do so, he/she should be happy with > an > old ICS release version. > > There needs to be a time that we look further into the future and leave > the > past in the past. Othwerwise we would be stuck in the past. > > Best Regards, > > SubZ Well... it's not that simple... i've been working for french mobile phone provider. They have some applications - heavy ones as it mixes helpdesk, commercial stuff, etc... - developped with delphi 5. Having a look at how they manage their project, the quality checks that are made, the time taken for any process involving an application evolution, that may take quite a lot of time. Moreover, migrating such an application would cost *a lot* of money in : - quality checks for the new compiler version ; - adapting applications to work with a new compiler version (there're millions lines of code, even in delphi) ; - if there're 3rd party components used, you have to be sure that those components work with the new compiler version, which is *never* guaranteed ; - checking the new compiled version of the application ; - deploying the new application on more than 1000 workstations ; - checking every bug, etc... Those applications i'm talking about are part of the company backbone. So when you think about the cost of migrating an application, when you think that the first goal of such companies is making money spending it lessly possible, adding a feature using TCP/IP component is less expensive using the same compiler - which has passed all the quality checks - than the one used for the application. that's why many companies are still using old versions of delphi. You both are quite talking in a developper way, in a technical way - no offense here ;). My talking is much more as a company manager which has to take in account every cost. Developping an application - and most of all anticipating its evolutions - is a loadbalancing between technical stuff and financial stuff. ICS, whatever its version, is a simple - hence robust - Winsock API. it may surely be found in many - unknown to us - company information systems backbone. So if there're modifications - bug correction for example - you have to be sure that the new version will still be backward compatible for what already exists. I don't mean the new functionnalities, but at least the actual ones. So yes, actually, some professional developpers still use old compilers and may need the components to still work, even with a new version. IMHO, 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 -- 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
Re: [twsocket] component question
- Original Message -
From: "Francois Piette" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, August 17, 2005 3:01 PM
Subject: Re: [twsocket] component question
> You have to change TFtpProgress data type to use an int64. Don't forget to
> rebuild the package and
> reinstall it so that delphi use the correct version.
>
> btw: How have you changed to int64 ?
> You should have replaced all integer or LongInt by a new custom type which
> is conditionnaly defined.
> Similar to this:
>
> {$IFDEF COMPILER6_UP}
>{$DEFINE Use64BitFiles}
> {$ENDIF}
>
> {$IFDEF Use64BitFiles}
>FtpInteger = int64;
> {$ELSE}
>FtpInteger = integer;
> {$ENDIF}
>
> and later in the code use FtpInteger where 64 bit is desirable.
> Doing so make the code compatible with older compiler version.
> You can easily to a search and replace of your int64 by FtpInteger.
>
If there are any StrToInt make sure they are change to StrToInt64 too.
Dan
--
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
Re: [twsocket] HttpCli: Opinion wanted !
Hi Angus I use CBuilder 4.0. It is due to company politics using Microsoft only (except for what have already is in use). Foolish, but true. Regards Kim - Original Message - From: "Angus Robertson - Magenta Systems Ltd" <[EMAIL PROTECTED]> To: Sent: Wednesday, August 17, 2005 3:00 PM Subject: [ZS2] Re: [twsocket] HttpCli: Opinion wanted ! > > Because there are still a lot of people using old compilers, > > frequently to maintain existing > > applications but also to develop new ones, even with Delphi 1 which is > > used for embedded systems using Win 3.x !! > > OK, can all those in this list using Delphi compilers earlier than > Delphi 5, Delphi 1 in particular, please respond to this message and > indicate why you want to continue using a six to 10 year old compiler > with the latest bugs and features for ICS? > > I'm really referring to professional developers here, not hobiests who > may be unable to afford a new version. > > If there are fewer than say a dozen positive responses, I'd suggest we > finally accept this argument for complicating and stalling development > of ICS by supporting obsolete compilers is finally put to rest. > > We can not stay stuck in past, we need to look to the future. > > Angus > > -- > 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 > -- 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
Re: [twsocket] R: HttpCli: Opinion wanted !
> This is a useless discussion. Only because you don't agree with your customers, and free helpers. For your convenience, you want to inconvience others. Angus -- 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
Re: [twsocket] HttpCli: Opinion wanted !
> Anyway, search for the message with subject "Re: [twsocket] Installing > ICS under windows 3.11" > posted earlier today and you have one recent user still using Delphi 1. No-one is going to stop people using old ICS versions on old compilers. If such users really need bug fixes they can always merge those they need into their old code from the latest version themselves. The question is whether current users that need new features should suffer to keep those one or two users on obsolete compilers happy. Borland stops support of old compilers very quickly, even Delphi 7 is obsolete as far as bug fixes are concerned. Yet you still want to support Delphi 1. Angus -- 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
Re: [twsocket] HttpCli: Opinion wanted !
> The question is whether current users that need new features should > suffer to keep those one or two users on obsolete compilers happy. You are wrong. Current user doesn't suffer because of old compiler support. Never. > Borland stops support of old compilers very quickly, even > Delphi 7 is obsolete as far as bug fixes are concerned. Borland earn money selling their upgrades. That's why they stop supporting old compiler as fast as possible. Lot's of people complain about that. Borland want you to use, no sorry, to BUY their upgrade to the latest version. As want most software vendors. That's business. And ICS is no business. -- [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://www.overbyte.be
Re: [twsocket] HttpCli: Opinion wanted !
Angus Robertson - Magenta Systems Ltd wrote: >> Anyway, search for the message with subject "Re: [twsocket] Installing >> ICS under windows 3.11" >> posted earlier today and you have one recent user still using Delphi 1. > > No-one is going to stop people using old ICS versions on old compilers. > > If such users really need bug fixes they can always merge those they > need into their old code from the latest version themselves. Agreed, nothing is for ever. Once you have to make a cut. I do not understand why all compilers needs to be supported by one single code base, especially not when old compliler can not benefit from new features. Arno Garrels > The question is whether current users that need new features should > suffer to keep those one or two users on obsolete compilers happy. > > Borland stops support of old compilers very quickly, even Delphi 7 is > obsolete as far as bug fixes are concerned. Yet you still want to > support Delphi 1. > > Angus -- 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
Re: [twsocket] HttpCli: Opinion wanted !
> > The question is whether current users that need new features should > > suffer to keep those one or two users on obsolete compilers happy. > > You are wrong. Current user doesn't suffer because of old compiler > support. Never. Sorry, I disagree. Whenever I make improvements to ICS source, it takes much longer than necessary due to complexity of the conditional statements and trying to forget to use statements that don't exist in obsolete versions of Delphi, and tying to provide workarounds in order to maintain this compatibility. My extended MIME decode was a good example, I used dynamic arrays because they are very versatile and don't need any clean-up (Delphi 4 and later), but you declined to add it to ICS unless I wasted my time rewriting the code using TLists instead. I'm afraid I decided it was not worth more of my time to meet your backward compatibility requirements. There have been other similar requirements from you. So I suffer. As do others attempting to maintain the source. > And ICS is no business. Many developers depend upon ICS for their business. Many more ignore ICS because they see it as a hobbists toy, with no proper documentation or current help, and buy commercial products instead. Very sad. Angus -- 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
Re: [twsocket] TWSocket DNSLookup
Hello Francois,
> The code is OK for both those using OnError and those using exception
> handling, IMO.
Yes, but behaviour is different. In this case (ok it is stupid from
programmer's view to not check it, but..) DNSLookupDone is only called
with an error if event handler is assigned to OnError, which normally is
not the case for someone who can deal with exceptions.
I have no problem with it (code has always been like this), but I think
an emtpy host name should call DNSLookup with an error in any case, not
only when OnError has a handler.
... or never, but I think behavour should be same with or without
assigned OnError... Oh whell it is only a minor thing...
My yongest son will married tomorrow for law (saterday for church), so
I'm very busy with other "exceptions" for the party etc.. :) Hell I
still have to search if I have a cravate...
---
Rgds, Wilfried
http://www.mestdagh.biz
Wednesday, August 17, 2005, 13:20, Francois Piette wrote:
>> Assign something on the OnError is not the way to go. Should the
>> RaiseException line not be commented out ? What do you think ?
> The code is OK for both those using OnError and those using exception
> handling, IMO.
> --
> [EMAIL PROTECTED]
> http://www.overbyte.be
> - Original Message -
> From: "Wilfried Mestdagh" <[EMAIL PROTECTED]>
> To:
> Sent: Wednesday, August 17, 2005 11:57 AM
> Subject: [twsocket] TWSocket DNSLookup
>> Hello Francois,
>>
>> Strange after all these years I did not check the AHostName before
>> calling DNSLookup for the first time :)
>>
>> Anyway there is something I wonder. First exception is raised, then
>> TriggerDnsLookupDone is called with the right argument, however because
>> the exception it is never called, and it should be with or without
>> error.
>>
>> Assign something on the OnError is not the way to go. Should the
>> RaiseException line not be commented out ? What do you think ?
>>
>> procedure TCustomWSocket.DnsLookup(const AHostName : String);
>> var
>> IPAddr : TInAddr;
>> HostName : String;
>> begin
>> if AHostName = '' then begin
>> RaiseException('DNS lookup: invalid host name.'); // comment ?
>> TriggerDnsLookupDone(WSAEINVAL);
>> Exit;
>> end;
>>
>> --
>> Rgds, Wilfried
>> http://www.mestdagh.biz
>>
>> --
>> 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
--
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
Re: [twsocket] R: HttpCli: Opinion wanted !
Hello Angus, >> This is a useless discussion. > Only because you don't agree with your customers, and free helpers. > For your convenience, you want to inconvience others. In fact it is useless, but please keep on reading! Part is that pro and not pro developpers are discussed but not circumstances. For example if I have to maintain an application written in Delphi 1..4 then customar will pay for D7 upgrade. But I'm speaking on a "normal" customar. Some time back I hade a very very large project for the gouverment. I think it is 2..3 year back. And it has to work on windows 3.11 It was for me have it or trow a very lot of money away, and I'm not speaking of commercial references for that project. Large projects for gouverment done feels good for representatives ! So I re-installed Delphi 1 for it :) About Delphi upgrades, I know a lots of amateurs programming for hobby that does lots faster Delphi upgrades than me (BTW: I'm really pro :) because they have more time than me for these things. About the components. I think older compilers may be dropped, at certain moment, only people have to be warned that they dont do a fresh upgrade into their older compilers if they need it. --- Rgds, Wilfried http://www.mestdagh.biz -- 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
[twsocket] XLMHTTPRequest
I would like to thank Francois and Wilfried for their notices... TCP server and client work without any problem. My other question. Using http connection in a real time application with a lot of pictures (you know what customers are interesting about) is very slow... I am considering to use XLMHTTPRequest for to change some values in a window more quickly. What I know all browsers are able to use this request from a Java script. Not using IIS server from Microsoft with ASP I have a problem how to implement it to HttpSrv component. Do someone knows how it works? I obtained a lot of sites asking Google, but all of them were about clients. I believe there is an easier way than to catch packets Regards Igor -- 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
Re: [twsocket] XLMHTTPRequest
As far as I understand, its just an HTTP GET request on the side of the server. The difference is in the client: it allows dynamic and asynchroneous requests without having to reload the entire main document. dZ. On Aug 17, 2005, at 17:04, Igor Pokorny wrote: > I would like to thank Francois and Wilfried for their notices... TCP > server and client work without any problem. > > My other question. > > Using http connection in a real time application with a lot of pictures > (you know what customers are interesting about) is very slow... > I am considering to use XLMHTTPRequest for to change some values in a > window more quickly. What I know all browsers are able to use this > request from a Java script. > Not using IIS server from Microsoft with ASP I have a problem how to > implement it to HttpSrv component. Do someone knows how it works? > I obtained a lot of sites asking Google, but all of them were about > clients. I believe there is an easier way than to catch packets > > Regards > > Igor > -- > 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 > -- 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
Re: [twsocket] HttpCli: Opinion wanted !
On 17-Aug-05 10:32:00 Angus Robertson - Magenta Systems Ltd wrote: >> How do you think that all we heavily tested for weeks if nobody, >> except the developer(s), made any test? >I only have a single development environment, and I need to be able to >produce bug fix versions of several applications at short notice, often >hours, that get widely distributed within hours. >Many other professional developers are probably in exactly the same >situation. I'm one. Actually I'm using only the HttpCli component. To do a test I normally use a modified version of HttpTst. To not affect the compilation of other application I copy the new files (HttpProt in this case) to the dir of the test application. With this way only this program will use the "new" version, so the other projects are "safe". >So using new versions of components is very delicate, thus the absolute >need for backward compatibly and full version and change documentation, >to allow the risk of new versions to be accessed. The changes that I made are backward compatible. If they aren't then there is a bug. >I do keep up to date with official ICS betas, including SSL, test them >for weeks or months in various live applications, report problems, and >often try to fix them myself, for the benefit of other uses, but only >if I can see the risk of doing so and I can be sure the changes will >not cause me major grief. This exactly what I normally do, and what every good programmer should do :-) BTW, there is another "test" version of HttpCli. If you missed it, this solve a potential problem that could raise when both the proxy and the host require an authentication. The symptom is very bad: the application goes in a infinite loop! So it is very important that people test it because it change the logic of how the autentication is handled internally. I worked two weeks to solve it. It take so long because I repeated the test with an huge amount of combination every time I changed the code. See old post for details. >> We are not speaking specific on gzip but on handlig encoding in a >> generic way. >Not really fussed how many different fancy schemes are supported. This was not only a problem of different encoding, but of different implementation. What I want to avoid is that an application need two different zip libraries because the component "need" a different one to handle the gzip encoding. And this will help a lot in the compability field, in particular when it is planned to use a different zip library in the future. >> If you are using VCLZip library to handle gzip content then it could >> be interesting to see if you are able to add it to this "new" version >> or if it is missing something indispensable. >Vclzip is commercial, I used it to replace the previous Borland Zlib >implementation because it was convenient, but I'd rather use open >source for anything new. >I will test your changed component in one of my applications provided, >provided there is no DLL requirement. There is no need of dll. To test it you need HttpProt.pas and HttpContCod.pas contained in HttpContCod.zip that is on ICS site. To use the new code you must define Use_ContentCoding, otherwise the code is exactly the same of the last release (and of course in that case there is no need of the HttpContCod unit). Using only these units no encodings will handled by the component, so all should be backward compatible. To enable an encoding you must include in the uses clause of one unit of your project a unit that contain a class able to handle, for example, the gzip. The HttpCCodGzip.pas is a sample. To work it need all other files contained in the zip, dll included. I invite you to test it first without gzip and then with gzip using the VCLZip library. To implement it write a new unit following HttpCCodGzip.pas as sample. It should be very easy (that unit is only 59 lines long). If you have questions I'm there. Of course feedback are welcome :-) 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
Re: [twsocket] HttpCli content encoding
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
Re: [twsocket] R: HttpCli: Opinion wanted !
On 17-Aug-05 14:54:56 Francois Piette wrote: [...] >The opinion I want to hear is about the design decisions that need to be done >about the HTTP client component supporting compression. See Maurizio messages >and answer to the technical questions he ask. Don't forget to answer to Set properties vs VFI :-) 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
Re: [twsocket] XLMHTTPRequest
> I obtained a lot of sites asking Google, but all of > them were about clients. Of course, XMLHTTPRequest is an operation done at client side. A script request data from an XML document. There is no special support needed at server side. It just receive more HTTP request from client. The fact that those request are generated by a javascript script is transparent. See this http://jibbering.com/2002/4/httprequest.html -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: "Igor Pokorny" <[EMAIL PROTECTED]> To: Sent: Wednesday, August 17, 2005 11:04 PM Subject: [twsocket] XLMHTTPRequest > I would like to thank Francois and Wilfried for their notices... TCP > server and client work without any problem. > > My other question. > > Using http connection in a real time application with a lot of pictures > (you know what customers are interesting about) is very slow... > I am considering to use XLMHTTPRequest for to change some values in a > window more quickly. What I know all browsers are able to use this > request from a Java script. > Not using IIS server from Microsoft with ASP I have a problem how to > implement it to HttpSrv component. Do someone knows how it works? > I obtained a lot of sites asking Google, but all of them were about > clients. I believe there is an easier way than to catch packets > > Regards > > Igor > -- > 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 -- 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
