Re: winsock.ew & localhost

new topic     » goto parent     » topic index » view thread      » older message » newer message

At 06:12 PM 10/8/98 EDT, you wrote:
>>Think it was just two winsock calls, initiating the winsock and
>>calling it to open the socket 127.0.0.1 at port whatever
>
>I'm not sure, but I think unless you have a server application listening
>at a port, nothing will pick up and you'll get a winsock error.
>
>I have a webserver running locally, and it listens on port 80. So if I
>had a Eu proggie connect to port 80, the webserver would pick it up.
>
>One thing you can try is run a webserver locally (make sure you have
>TCP/IP installed), then use telnet to connect to 127.0.0.1:80. The
>webserver will pick up. Then type a command used in the HTTP protocol,
>and you'll get something back. Try reading the HTTP RFC (sorry, don't
>know the number) for a list of valid commands.
>
>So if you have no server apps, it won't work :)

I had *2* applications listening to 127.0.0.1 on a specified port.

My euphoria program [could] connect to 127.0.0.1 when I was online, the
other applications would accept the socket connection, etc.

They would *not* recieve the request when I was offline, and winsock.ew
would return SOCKET_ERROR.

I know it can be done, I've done it many times before; i just have no idea
how to do it in Euphoria.

FD (censored)

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu