Francois PIETTE wrote:
>> That makes me think we need a throttle at the root (TWSocket).
>
> Would be interesting.
Will think about it.
>
>> Just switched the roles, installed the mail server on a slow(er) box
>> and ran the TSmtpCli application on the fast(er) one. CPU use of the
>> TSmtpCli a
Hello Arno,
1GB networks are very difficult to tune as many hardware behind the
network cards can't handle such high speed, for example hard drives on
"client" machines usually can't handle full 1Gb speed reception and
will stay at average 80-100Mb only this making different bottlenecks
on
> > Try setting the network speed to 10 Mbps (you should be able to set
> > the speed in the hardware config).
>
> I changed it from Autodetect to 10 MBit/s full duplex. There's now
> just 0-1% CPU use
So cleary now your are in a network bound situation.
With 100 Mbps your are still in network bou
Are there any plans for the near future ?
Paul
- Original Message -
From: "Francois Piette"
To: "ICS support mailing"
Sent: Tuesday, July 14, 2009 11:53 AM
Subject: Re: [twsocket] Ipv6
Any plans yet ?
Not yet.
btw: Does OpenSSL support IPv6 ?
--
francois.pie...@overbyte.be
Auth
Paul wrote:
> Are there any plans for the near future ?
If ICS shall not die very soon it has to be implemented anyway!
I haven't yet got complains, however I agree that it should be
put on top of the todo list.
IMO, it cannot be done without breaking existing user code.
--
Arno Garrels
>
>
Hello,
Maybe we can derive new components from the existing ones for IPv6? This
would preserve compatibility.
Regards,
SZ
On Wed, Jul 15, 2009 at 4:56 PM, Arno Garrels wrote:
> Paul wrote:
> > Are there any plans for the near future ?
>
> If ICS shall not die very soon it has to be implemente
Francois Piette wrote:
>> Regarding the hard coded boundary strings I suggest to
>> make them (or parts) component properties.
>
> Would be a good idea to create a property XMailer with that string.
> The default value would be the current value. Some trick should be
> used so that the correct com
Dod wrote:
> Hello Arno,
>
> 1GB networks are very difficult to tune as many hardware behind the
> network cards can't handle such high speed, for example hard drives on
> "client" machines usually can't handle full 1Gb speed reception and
> will stay at average 80-100Mb only this making d
Hi , i'm using the MultipartHttpDownloader component in my application ,But
i want to know how to be able to download multiple Files
--
Many thanks
-
Yours Randy
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/
> Francois said...
> 1- You should try to send the email, with the exact
> same program, from another computer (or even several
> computers) using another ISP
> 2- It is likely that - despite what they say - your
> IP or hostname is blacklisted.
Thanks for the input Francois. I have indeed test
> Arno said...
> If ICS shall not die very soon it has to be implemented anyway!
Wow! Scared of that statement! What do you mean by that? Is ICS in danger
of going away?
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/list
Hi , i'm using the MultipartHttpDownloader component in my application
,But
i want to know how to be able to download multiple Files
As with regular HTTP client: use one component per file.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of th
That's probably what I saw today. However all interfaces were set to
10 MBit/s mode, may be caused by the switch?
Yes, the switch has also to be forced to 10 Mbps.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Compon
If ICS shall not die very soon it has to be implemented anyway!
Wow! Scared of that statement! What do you mean by that?
Is ICS in danger of going away?
Not at all.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet
Hoby Smith wrote:
>> Arno said...
>> If ICS shall not die very soon it has to be implemented anyway!
>
> Wow! Scared of that statement! What do you mean by that? Is ICS in
> danger of going away?
No, not as long as there are people using and supporting it actively.
However users will move to a
Здравствуйте, Twsocket.
--
С уважением,
Actionmanager mailto:actionmana...@gmail.com
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
I don't think it's very urgent, but the complaint I got from a US customer
says that it's use is on the way.
Paul
- Original Message -
From: "Arno Garrels"
No, not as long as there are people using and supporting it actively.
However users will move to another component suite when t
Hello!
> No, not as long as there are people using and supporting it actively.
> However users will move to another component suite when they need basic
> features not included in ICS. IMO IPv6 will become such a basic feature
> rather soon. Competitors of ICS already support IPv6.
And IMAP4 :>
Piotr Dałek wrote:
> Hello!
>
>> No, not as long as there are people using and supporting it actively.
>> However users will move to another component suite when they need
>> basic
>> features not included in ICS. IMO IPv6 will become such a basic
>> feature rather soon. Competitors of ICS alread
Well, I finally resolved this issue. What a pain. In the end, the problem
was just character data that GoDaddy didn't like. It would have been nice
if their SMTP response had said something like, "Invalid character data
detected", instead of, "Rejected due to spam or virus content". But, maybe
Is there a problem having multiple instances of ICS socket objects on
the same thread? I have a Delphi app (single threaded) with different
ICS-based objects in various units. I saw today what looked like
crossover functionality between some of them. I'm getting TTimer access
violation errors t
21 matches
Mail list logo