Re: [WebDNA] TCPConnect Slowness

This WebDNA talk-list message is from

2013


It keeps the original formatting.
numero = 110112
interpreted = N
texte = It's been a while.... but from what I remember... HTTP 1.1 protocol uses persistent connections (check if you're setting = 1.1 or 1.0) Use 1.0 or you'll have to specify a KeepAlive directive in a header with = 1.1 - I don't remember the directive but essentially you want to specify = not to use KeepAlive - look it up The long delays are caused by the remote server expecting a persistent = connection (which WebDNA doesn't do) - so the request is having to time = out before the response is returned. =20 On Jan 22, 2013, at 12:57 PM, Michael Davis wrote: > Hi All, > Before I post a long message full of code I'll just ask if there = is a known issue. Has anyone experienced long delays using TCPConnect = to post data to a remote server? I have a particular TCPConnect that = takes 30 seconds to complete. When the same connection is made directly = in a web browser, it is instantaneous. So it's not a problem with the = remote server. >=20 > Mike >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] TCPConnect Slowness (aaronmichaelmusic@gmail.com 2013)
  2. Re: [WebDNA] TCPConnect Slowness (Daniel Meola 2013)
  3. [WebDNA] TCPConnect Slowness (Michael Davis 2013)
It's been a while.... but from what I remember... HTTP 1.1 protocol uses persistent connections (check if you're setting = 1.1 or 1.0) Use 1.0 or you'll have to specify a KeepAlive directive in a header with = 1.1 - I don't remember the directive but essentially you want to specify = not to use KeepAlive - look it up The long delays are caused by the remote server expecting a persistent = connection (which WebDNA doesn't do) - so the request is having to time = out before the response is returned. =20 On Jan 22, 2013, at 12:57 PM, Michael Davis wrote: > Hi All, > Before I post a long message full of code I'll just ask if there = is a known issue. Has anyone experienced long delays using TCPConnect = to post data to a remote server? I have a particular TCPConnect that = takes 30 seconds to complete. When the same connection is made directly = in a web browser, it is instantaneous. So it's not a problem with the = remote server. >=20 > Mike >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us aaronmichaelmusic@gmail.com

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

where to put code (1998) RE: [WebDNA] Problem with Cookies in IE and Safari (2009) Determining Method (2000) Re:quit command on NT (1997) [IpAddress] Tag (1997) Nested tags count question (1997) new PurgeDatabase command? (was NT vs Mac) (1997) searching more then one (1999) WebCatalog NT beta 18 problem (1997) Extended [ConvertChars] (1997) [SHOWIF AND/OR] (1997) Protect (1997) Remove from list server (1997) converting dates in database (1998) Merging databases (1997) Euro WebDNA Conference (2004) Webcat Crashing Error 1701 (2000) Help! WebCat2 bug (1997) I'm tired of all this! (2000) [WebDNA] Test - Getting double messages??? (2008)