After reading Marco's message, I was curious about
why wsockets.pas adds 60K of file size. When I looked
at the file, I didn't really see NOFORM. Didn't see
any unnecessary units either...
MvdV> .
MvdV> wsocketS imports unit controls without using it (or is it for the
USE_SSL?)
MvdV>
> > Only used. I even deleted all ICS dcu files.
>
> I created a new console mode application (D7), added NOFORMS in the project
> defines.
> Compilation gives a filesize: 39.424 Bytes.
> Added WSocket to the uses clause: 91.136 Bytes.
> Added WSocketS to the uses clause: 91.648 Bytes.
> Removed
A new ICS version is available.
A small bug has been fixed in the HTTP client component that affected
authentication with iPlanet Web Proxy Server (found by Mr Bloms and
Tomachinsky).
A new console mode sample: ConUdpLstn. It is the GUI sample UdpLstn ported
to console. It make use on the TConAppli
Thanks Francois for the testing.
Arno was right. Once I updated to the latest ICS,
the file size went down to 127KB (Delphi 5.)
Before I used TWSocketServer it was 61KB. Not sure
why it doubled the file size. But it's still a lot better
than before, which was over 300KB. I added some lines of
cod
Fastream Technologies wrote:
But this is a decision that affects ICS developers since MS is the
owner of the OS and Winsock therefore can shed some light with its
design. I did not have any malign intentions.
Be that as it may, discussions of the /design decisions/ that lead to
the current state
Francois PIETTE wrote:
>> I did some further testing.
>>
>> I commented out most of my code so it's not doing
>> anything. When I only have WSocket in uses clause,
>> the file size is 61KB. The moment I put WSocketS in,
>> the file size jumps to 288KB (on D5.) This is when
>> no function of ICS is
> I did some further testing.
>
> I commented out most of my code so it's not doing
> anything. When I only have WSocket in uses clause,
> the file size is 61KB. The moment I put WSocketS in,
> the file size jumps to 288KB (on D5.) This is when
> no function of ICS is being called, no object create
Thank you, I will inspect my settings, because in this machine other FTP
programs failed, too.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francois Piette
Sent: Thursday, April 14, 2005 11:45 AM
To: ICS support mailing
Subject: Re: [twsocket] FTP Con
But this is a decision that affects ICS developers since MS is the owner of
the OS and Winsock therefore can shed some light with its design. I did not
have any malign intentions.
Regards,
SZ
- Original Message -
From: "Francois Piette" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sen
> I have a slow FTP connection (typically the connection lasts about 60 sec
> using for example Total
Commander). I tried to connect using ICS FTP component, but after about 15 sec
I receive "Error code
10060 - Connection Timed out".
> I changed the timeout property of the FTP component to 60, bu
> why did MS chose threads?
This is not the place to discuss Microsoft design decision.
Please use a general purpose mailing list or newsgroup for that topic.
Please focus on ICS !
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Fastream Technologies" <[EMAIL P
You seem to be right and I can understand why Apache has chosen threaded way
(for UNIX compatibility) but why did MS chose threads? What about I/O
optimization. For example async freezes when a buffer of I/O is being read
whereas threads to better disk/socket I/O?
SZ
- Original Message
Hi!
I have a slow FTP connection (typically the connection lasts about 60 sec using
for example Total Commander). I tried to connect using ICS FTP component, but
after about 15 sec I receive "Error code 10060 - Connection Timed out".
I changed the timeout property of the FTP component to 60, but
> Well, async cannot take advantage of multi-processor systems.
> Also for CGI and ISAPI execution, threads seem to be a better
> way. And all the commercial Web servers I know such as IIS
> and Apache chose it for these reasons.
You are mixing up two factors.
Even on multi-processor system, o
Hello,
Well, async cannot take advantage of multi-processor systems. Also for CGI
and ISAPI execution, threads seem to be a better way. And all the commercial
Web servers I know such as IIS and Apache chose it for these reasons.
Best Regards,
SZ
- Original Message -
From: "Bjørnar Niels
> because there are alot of records to check, i wanted it to be threaded...
Well, this is defenitely not a case where multithreading is needed because ICS
HTTP component is
asynchronous. HTTP component doesn't block ! It automatically handle your
requests in the background
using events. If you n
> The only shortcoming of ICS is the web server which has no official and/or
optimized CGI/ISAPI
> component and by design async which is bad for a web server.
SZ, why do you think async design is bad for a webserver?
Regards Bjørnar
--
To unsubscribe or change your settings for TWSocket m
17 matches
Mail list logo
