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:

I think WebDNA-Talk died ... :( (1997) Counting records (2000) writing orders to a db (1997) WebSTAR 2.1 freezes my Mac (1997) WebCat cannot handle compatible search parameters? (1997) find with exceptions (1997) Template not found error messages (1997) HELP WITH DATES (1997) [WebDNA] .htm files (2008) More news on 5.0 (2003) NT version and O'reily's WebSite (1997) [WebDNA] MIDDLE problems (2012) includes and cart numbers (1997) WebCatalog [FoundItems] Problem - AGAIN - (1997) WebCat and image maps (1997) NT vs Mac (1997) Reminder... (2003) Error handling for accountNum (1997) RE: Nesting [ListFiles] (1998) emailer error -108 (1997)