use-livecode Digest, Vol 179, Issue 47

[Douglas Ruisaard]

Thanks, Mark .. but "the result" returns NOTHING in either a distorted Google or local call.. BOTH of which are, indeed,  DNS "errors" not strictly "socket" errors... thanks for that insight!

I'll go back to using tsnet for this other project.  I can time it out and use send" a dummy request to test the connection.

Cheers!

Douglas Ruisaard
Trilogy Software
(250) 573-3935


> From: Mark Wieder <ahsoftware at sonic.net>
> To: Douglas Ruisaard via use-livecode <use-livecode at lists.runrev.com>
> Subject: Re: Socket questions
> Message-ID: <ad830e5f-3eb9-587e-8147-cc7cf8954b7f at sonic.net>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 08/18/2018 01:38 PM, Douglas Ruisaard via use-livecode wrote:
> 
> > However, if I substitute "www.googleXXX.com:80" as the socket ID (or distort *my* ESP8266 ID to a
> non-existent one), I would have expected some sort of error message... trapped by the "socketError"
> handler ... but I get nothing.
> 
> That's a dns lookup failure, which won't get as far as a socketError
> message. What you should get instead is a non-empty result message from
> the openSocket command. I can't comment on tsNet, but libUrl has never
> to my recollection actually done this correctly.
> 
> --
>   Mark Wieder
>   ahsoftware at gmail.com
> 
> 
>