|
Log in | ||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Hi,
the tffClient timeout was too big (100,000). I didnīt know that the client timeout interferes in the ConectionManager time to established connection. This is not good, because I need a short timeout when CM is searching the FFserver and after that a larger timeout to guarantee that the application wonīt get "timeouts'. Is there any way to tell CM not check the tffClient timeout, i.e., set a different timeout for CM ? -- Best regards Sergei Safar ---------- Hi Eivind, there are two machines connected via a twisted pair cable, there is no adsl or dialup connections to cause long broadcasts delays. I am experiencing some troubles with CM, because it tooks too much time to connect to FFserver ( more than one minute) when the protocol is TCP/IP. FFexplorer can find FFserver (TCP/IP) in 2 seconds. I really donīt know where the problem is. Any help here would be appreciated. Best regards, Sergei Safar |
|
#2
|
|||
|
|||
|
Replied to in the proper newsgroup.
-- Eivind Bakkestuen [NDD] Please, no email unless requested. Search Borland and third-party newsgroups here: www.tamaracka.com "Sergei Safar" <sergei@no_spam_hissa59@ig.com.br> wrote in message news:3eb48049@wic040d.... > Hi, > > the tffClient timeout was too big (100,000). I didnīt know that the client timeout interferes in the ConectionManager time to > established connection. This is not good, because I need a short timeout when CM is searching the FFserver and after that a > larger timeout to guarantee that the application wonīt get "timeouts'. > > Is there any way to tell CM not check the tffClient timeout, i.e., set a different timeout for CM ? > > -- > Best regards > > Sergei Safar > ---------- > > Hi Eivind, > > there are two machines connected via a twisted pair cable, there is no adsl or dialup connections to cause long broadcasts > delays. I am experiencing some troubles with CM, because it tooks too much time to connect to FFserver ( more than one > minute) when the protocol is TCP/IP. FFexplorer can find FFserver (TCP/IP) in 2 seconds. > > I really donīt know where the problem is. Any help here would be appreciated. > > Best regards, > > Sergei Safar > > > |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| WideString problem not solved | Petr Manas | nexusdb.public.support.odbc | 1 | 14th September 2005 11:30 AM |