Re: [twsocket] Compiling latest ICS-beta
Hello,
> I also get error in HttpContCod.hpp on
>
> __property bool Active = {read=GetActive, nodefault}; (line 85)
> __property AnsiString Coding = {read=GetCoding}; (line 86)
>
> The error is parameter mismatch.
With today's beta (March 9th) I get the above errors as well. Anyone has
found a cure for this?
Regards,
SZ
--
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] Odd Behaviour
Hi Arno Garrels, >> I still haven't got your configuration and the problem completely. >> As far as I understand the FTP server in question >> is listining on port 5014. >> It has active connections downloading files, but one of your clients >> gets a 10061 when it tries to connect, is that correct? What you have understood is correct. But just this is not the odd behaviour. I have another FTP server listening at 5011 on the same machine where 5014 is listening. The funny thing is that the problematic client which has two FTP Clients conneted at 5011 and 5014 can send files to the FTP server at 5011 but not at 5014 ? Further Clarification if required only: You may wonder why I am using two FTP Servers. As I have mentioned earlier I have the MyNode.exe which works at port 5011 on all 5 machines, therefore each machine has a FTP server listening at 5011 and a FTP Client sending at port 5011. Whereas MyServer.exe is required only for the UserInterface rarely and this had FTP Server on port 5014. My Application is for Automatic backups and the backups are stored from each machine on to any selected machine/s. Regards Allan ___ NEW Yahoo! Cars - sell your car and browse thousands of new and used cars online! http://uk.cars.yahoo.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] Compiling latest ICS-beta
Bjørnar Nielsen wrote:
> The problemt with the constants that were defined in both Winsock.pas and
> WSoscket.pas went away after commenting them out in WSocket.pas. I think
> Francois agreed on removing them from WSocket.pas.
IOCPARM_MASK
IOC_VOID
IOC_OUT
IOC_IN
IOC_INOUT
Above constants have been removed from WSocket.pas the version before last.
---
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
> The other fault with parameter mismatch with Active and Coding in
> HttpContCod.hpp I have no sollution for. I just commented them out in the
> pas-file since I for now don't need content encoding. I also would like a
> fix for this to be able to use these properties.
> Regards Bjørnar
>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Merijn Terheggen
>> Sent: 10. mars 2006 13:54
>> To: ICS support mailing
>> Subject: Re: [twsocket] Compiling latest ICS-beta
>>
>> I also get the same parameter mismatch errors in BCB6 that
>> Bjørnar mentioned in his mail.
>>
>> Any ideas?
>> Bjørnar: are these errors gone in your set-up now? What did you do?
>>
>> I used the 20060309 beta and the forementioned constants are
>> commented-out (I checked it).
>>
>> On 1/27/06, Bjørnar Nielsen <[EMAIL PROTECTED]> wrote:
>>>
>>> I downloaded and installed latest beta and I found these problems
>>> (using BCB6).
>>>
>>> The package compiled fine but I get errors when using ICS in a
>>> testproject in WSocket.hpp on these:
>>>
>>> IOCPARM_MASK
>>> IOC_VOID
>>> IOC_OUT
>>> IOC_IN
>>> IOC_INOUT
>>>
>>> They are defined in both Winsock.pas and WSoscket.pas. When I removed
>>> them from WSocket.pas the errors was gone.
>>>
>>> I also get error in HttpContCod.hpp on
>>>
>>> __property bool Active = {read=GetActive, nodefault}; (line 85)
>>> __property AnsiString Coding = {read=GetCoding}; (line 86)
>>>
>>> The error is parameter mismatch.
>>>
>>> Regards Bjørnar
>>>
>>>
>>>
>>> --
>>> 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
Re: [twsocket] Compiling latest ICS-beta
The problemt with the constants that were defined in both Winsock.pas and
WSoscket.pas went away after commenting them out in WSocket.pas. I think
Francois agreed on removing them from WSocket.pas.
The other fault with parameter mismatch with Active and Coding in
HttpContCod.hpp I have no sollution for. I just commented them out in the
pas-file since I for now don't need content encoding. I also would like a
fix for this to be able to use these properties.
Regards Bjørnar
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Merijn Terheggen
> Sent: 10. mars 2006 13:54
> To: ICS support mailing
> Subject: Re: [twsocket] Compiling latest ICS-beta
>
> I also get the same parameter mismatch errors in BCB6 that
> Bjørnar mentioned in his mail.
>
> Any ideas?
> Bjørnar: are these errors gone in your set-up now? What did you do?
>
> I used the 20060309 beta and the forementioned constants are
> commented-out (I checked it).
>
> On 1/27/06, Bjørnar Nielsen <[EMAIL PROTECTED]> wrote:
> >
> > I downloaded and installed latest beta and I found these problems
> > (using BCB6).
> >
> > The package compiled fine but I get errors when using ICS in a
> > testproject in WSocket.hpp on these:
> >
> > IOCPARM_MASK
> > IOC_VOID
> > IOC_OUT
> > IOC_IN
> > IOC_INOUT
> >
> > They are defined in both Winsock.pas and WSoscket.pas. When
> I removed
> > them from WSocket.pas the errors was gone.
> >
> > I also get error in HttpContCod.hpp on
> >
> > __property bool Active = {read=GetActive, nodefault}; (line 85)
> > __property AnsiString Coding = {read=GetCoding}; (line 86)
> >
> > The error is parameter mismatch.
> >
> > Regards Bjørnar
> >
> >
> >
> > --
> > 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
Re: [twsocket] Compiling latest ICS-beta
I second both of you as I reported earlier.
Regards,
SZ
- Original Message -
From: "Merijn Terheggen" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Friday, March 10, 2006 2:54 PM
Subject: Re: [twsocket] Compiling latest ICS-beta
I also get the same parameter mismatch errors in BCB6 that Bjørnar mentioned
in his mail.
Any ideas?
Bjørnar: are these errors gone in your set-up now? What did you do?
I used the 20060309 beta and the forementioned constants are commented-out
(I checked it).
On 1/27/06, Bjørnar Nielsen <[EMAIL PROTECTED]> wrote:
>
> I downloaded and installed latest beta and I found these problems (using
> BCB6).
>
> The package compiled fine but I get errors when using ICS in a testproject
> in WSocket.hpp on these:
>
> IOCPARM_MASK
> IOC_VOID
> IOC_OUT
> IOC_IN
> IOC_INOUT
>
> They are defined in both Winsock.pas and WSoscket.pas. When I removed them
> from WSocket.pas the errors was gone.
>
> I also get error in HttpContCod.hpp on
>
> __property bool Active = {read=GetActive, nodefault}; (line 85)
> __property AnsiString Coding = {read=GetCoding}; (line 86)
>
> The error is parameter mismatch.
>
> Regards Bjørnar
>
>
>
> --
> 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
Re: [twsocket] Compiling latest ICS-beta
I also get the same parameter mismatch errors in BCB6 that Bjørnar mentioned
in his mail.
Any ideas?
Bjørnar: are these errors gone in your set-up now? What did you do?
I used the 20060309 beta and the forementioned constants are commented-out
(I checked it).
On 1/27/06, Bjørnar Nielsen <[EMAIL PROTECTED]> wrote:
>
> I downloaded and installed latest beta and I found these problems (using
> BCB6).
>
> The package compiled fine but I get errors when using ICS in a testproject
> in WSocket.hpp on these:
>
> IOCPARM_MASK
> IOC_VOID
> IOC_OUT
> IOC_IN
> IOC_INOUT
>
> They are defined in both Winsock.pas and WSoscket.pas. When I removed them
> from WSocket.pas the errors was gone.
>
> I also get error in HttpContCod.hpp on
>
> __property bool Active = {read=GetActive, nodefault}; (line 85)
> __property AnsiString Coding = {read=GetCoding}; (line 86)
>
> The error is parameter mismatch.
>
> Regards Bjørnar
>
>
>
> --
> 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] Charset in Mail header
On Mar 8, 2006, at 13:48, Paweł (WP) wrote: > But, I need to add something like this: > Content-type: text/html; charset=iso-8859-2 > > If I add this line to procedure "HtmlSmtpClientProcessHeader" it > brokes the email... You need to add the "charset" to only the MIME-part that will use that character set. Since you are putting it in the message (global) header itself, it breaks the MIME encapsulation. Multipart messages must use ASCII (the default), because all transport encapsulation is implemented in ascii, including MIME headers and boundaries. Changing the global charset of a message will force the client to translate the entire body, instead of the individual parts. dZ. -- 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] keepalive
Hello Wilfried, Here are some other infos that may help/explain TcpMaxDataRetransmissions Key: Tcpip\Parameters Value Type: REG_DWORD-Number Valid Range: 0-0x Default: 5 Description: This parameter controls the number of times TCP will retransmit an individual data segment (not connection request segments) before aborting the connection. The retransmission time-out is doubled with each successive retransmission on a connection. It is reset when responses resume. The base time-out value is dynamically determined by the measured round-trip time on the connection. KeepAliveInterval Key: Tcpip\Parameters Value Type: REG_DWORD-Time in milliseconds Valid Range: 1-0x Default: 1000 (one second) Description: This parameter determines the interval between keep-alive retransmissions until a response is received. Once a response is received, the delay until the next keep-alive transmission is again controlled by the value of KeepAliveTime. The connection will be aborted after the number of retransmissions specified by TcpMaxDataRetransmissions have gone unanswered. KeepAliveTime Key: Tcpip\Parameters Value Type: REG_DWORD-Time in milliseconds Valid Range: 1-0x Default: 7,200,000 (two hours) Description: The parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a keep-alive packet. If the remote system is still reachable and functioning, it will acknowledge the keep-alive transmission. Keep-alive packets are not sent by default. This feature may be enabled on a connection by an application. Dead Gateway Detection Dead gateway detection is used to allow TCP to detect failure of the default gateway and to make an adjustment to the IP routing table to use another default gateway. The Microsoft TCP/IP stack uses the TRIGGERED RESELECTION method described in RFC 816, with some slight modifications based upon customer experiences and feedback. When any TCP connection that is routed through the default gateway has attempted to send a TCP packet to the destination a number of times equal to one-half of the registry value TcpMaxDataRetransmissions, without receiving a response, the algorithm changes the Route Cache Entry (RCE) for that one remote IP address to use the next default gateway in the list. When 25 percent of the TCP connections have moved to the next default gateway, the algorithm advises IP to change the computer's default gateway to the one that the connections are now using. For example, assume that there are currently TCP connections to 11 different IP addresses that are being routed through the default gateway. Now assume that the default gateway fails, that there is a second default gateway configured, and that the value for TcpMaxDataRetransmissions is at the default of 5. When the first TCP connection tries to send data, it will not receive any acknowledgments. After the third retransmission, the RCE for that remote IP address will be switched to use the next default gateway in the list. At this point, any TCP connections to that one remote IP address will have switched over, but the remaining connections will still try to use the original default gateway. When the second TCP connection tries to send data, the same thing will happen. Now, two of the 11 RCEs will point to the new gateway. When the third TCP connection tries to send data, after the third retransmission, three of 11 RCEs will have been switched to the second default gateway. Because, at this point, over 25 percent of the RCEs have been moved, the default gateway for the whole computer will be moved to the new one. At this point, that default gateway remains the primary one for the computer until it experiences problems (causing the dead gateway algorithm to try the next one in the list again) or until the computer is restarted. When the search reaches the last default gateway, it returns to the beginning of the list. TCP Retransmission Behavior TCP starts a retransmission timer when each outbound segment is handed down to IP. If no acknowledgment has been received for the data in a given segment before the timer expires, then the segment is retransmitted. For new connection requests, the retransmission timer is initialized to 3 seconds, and the request (SYN) is resent up to TcpMaxConnectRetransmissions times (the default for Windows NT 5.0 is 2 times, down from 3 in Windows NT 4.0). On existing connections, the number of retransmissions is controlled by the TcpMaxDataRetransmissions registry parameter (5 by default). The retransmission time-out is adjusted "on the fly" to match the characteristics of the connection using Smoothed Round Trip Time (SRTT) calculations as described in RFC 793. The timer for
