Re: tcpconnect feature request ..

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 52412
interpreted = N
texte = This is interesting ... and I'll bet that it's not possible to add this feature because of the low level capabilities (and limitations) of the tcpconnect context.I think a redirect sends a response back to the browser that tells the browser to close the connection then immediately open a new connection on a different page (the redirect page). If this is how it works, then the connection will close after the browser receives the 'redirect' response from the server ... and the rest of the webdna code in your template will be interpreted and then sent to the browser.This means SMSI would have to come up with a feature that dynamically creates and inserts an *invisible* tcpconnect context immediately following the visible tcpconnect you have coded into your template. But it could only do this when the response from your tcpconnect context is a redirect instead of a 'normal' response.It's probably not impossible, but ... ?>Is there anyway we could get TCPCONNECT to have an optional>>&redirect=T so it would follow 302/303 redirects ?>>Just spent a couple of hours trouble shooting a Paypal IPN problem >and it turns out if the tcpconnect context followed a redirect no >error would have been found ..>>Thanks>Alain-- Sincerely,Kenneth Grome-------------------------------------------------------------Outsource your WebDNA programming for $18 an hour or less!--------------------------------------------------------------------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: tcpconnect feature request .. ( Alain Russell 2003)
Re: tcpconnect feature request .. ( Scott Anderson 2003)
Re: tcpconnect feature request .. ( Alain Russell 2003)
Re: tcpconnect feature request .. ( Kenneth Grome 2003)
tcpconnect feature request .. ( Alain Russell 2003)

This is interesting ... and I'll bet that it's not possible to add this feature because of the low level capabilities (and limitations) of the tcpconnect context.I think a redirect sends a response back to the browser that tells the browser to close the connection then immediately open a new connection on a different page (the redirect page). If this is how it works, then the connection will close after the browser receives the 'redirect' response from the server ... and the rest of the webdna code in your template will be interpreted and then sent to the browser.This means SMSI would have to come up with a feature that dynamically creates and inserts an *invisible* tcpconnect context immediately following the visible tcpconnect you have coded into your template. But it could only do this when the response from your tcpconnect context is a redirect instead of a 'normal' response.It's probably not impossible, but ... ?>Is there anyway we could get TCPCONNECT to have an optional>>&redirect=T so it would follow 302/303 redirects ?>>Just spent a couple of hours trouble shooting a Paypal IPN problem >and it turns out if the tcpconnect context followed a redirect no >error would have been found ..>>Thanks>Alain-- Sincerely,Kenneth Grome-------------------------------------------------------------Outsource your WebDNA programming for $18 an hour or less!--------------------------------------------------------------------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: tcpconnect feature request ..

2003

Top Articles:

Related Readings: