1. ASYNC SOCKETS
hi all,
i'm intending to change my proggy from using sync sockets to using Async
sockets. I have never coded any proggy that uses Async sockets now i'm
stuck.
i checked the archives and it looks like most proggys that use Async
sockets are servers.. Only one proggy namely AsyncHTTP by Thomas Parslow
could do client work while using Async Sockets. so i'm having problems
as Thomas's code is a bit !"!$%£$%£
Any way is their some one who can give me async tutorial for Euphoria,
i'm writing a telnet-like proggy for Euphoria.
Bytheway, has any one noticed you cannot connect to your local computer
if not on the internet using winsock.ew. Even if it can resolve your
hostname or IP address.
jordah
2. Re: ASYNC SOCKETS
- Posted by Robsz2 at aol.com
May 06, 2002
--has any one noticed you cannot connect to your local computer
--if not on the internet using winsock.ew. Even if it can resolve your
--hostname or IP address
^^^ ACTUALLY YES I HAVE ^^^
I also noticed that it will not let you connect to http://localhost/ or
http://127.0.0.1/
It only lets you connect to the IP address it returns.
3. Re: ASYNC SOCKETS
- Posted by Robsz2 at aol.com
May 07, 2002
--part1_aa.b262d09.2a0907a6_boundary
What part of it do you need help with? connecting? listening?
I'll try to help you the best I can. I have a little bit ofexperience with
AsyncHTTP.ew
If this is even the same thing your talking about -- I dont know. But I will
try to help you. If it isnt, send me the files so I can take a look at them.
--part1_aa.b262d09.2a0907a6_boundary
<HTML><FONT FACE=arial,helvetica><FONT SIZE=2>What part of it do you need help
with? connecting? listening?<BR>
<BR>
I'll try to help you the best I can. I have a </FONT><FONT
COLOR="#000000" style="BACKGROUND-COLOR: #ffffff" SIZE=1 FAMILY="SANSSERIF"
FACE="Arial" LANG="0">little </FONT><FONT COLOR="#000000"
style="BACKGROUND-COLOR: #ffffff" SIZE=2 FAMILY="SANSSERIF" FACE="Arial"
LANG="0">bit ofexperience with AsyncHTTP.ew<BR>
<BR>
--part1_aa.b262d09.2a0907a6_boundary--
4. Re: ASYNC SOCKETS
jordah ferguson wrote:
> ...
>
> Bytheway, has any one noticed you cannot connect to your local computer
> if not on the internet using winsock.ew. Even if it can resolve your
> hostname or IP address.
You *can* connect. Connect to "localhost", or "127.0.0.1". Of course you
must listen on some port. You can try to launch the Telnet server using async
sockets
by bjackson and telnet to 127.0.0.1 at port 23. If you cannot connect you can
have some
problem/firewall on your machine.
Martin
5. Re: ASYNC SOCKETS
On 9 May 2002, at 16:27, Martin Stachon wrote:
>
> jordah ferguson wrote:
> > ...
> >
> > Bytheway, has any one noticed you cannot connect to your local computer
> > if not on the internet using winsock.ew. Even if it can resolve your
> > hostname or IP address.
>
> You *can* connect. Connect to "localhost", or "127.0.0.1". Of course you
> must listen on some port. You can try to launch the Telnet server using async
> sockets by bjackson and telnet to 127.0.0.1 at port 23. If you cannot connect
> you can have some problem/firewall on your machine.
True, it is possible to mess up winsock in a way you cannot use localhost. I
do not know why this happens, but it happens for me with EInetLib_full.ew. I
suspect something is not released properly.
Kat
6. Re: ASYNC SOCKETS
- Posted by Robsz2 at aol.com
May 09, 2002
Well I do not have a firewall on my machine and i could not connect to
"localhost" or "127.0.0.1" using winsock on port 80. I keep getting a 404
server not found message. I have it set up so it sends out a web page to the
incoming connections. It has only work on the IP address it finds. I do not
know of any errors on my machine exept that it is very slow. Maybe its a
proxy thing? I do not have a proxy configured but i think AOL uses them? Or
maybe it a cache thing. I dont know. Maybe ill clear my TEMP and give it
another try one of these days.
7. Re: ASYNC SOCKETS
On 9 May 2002, at 17:44, Robsz2 at aol.com wrote:
>
> Well I do not have a firewall on my machine and i could not connect to
> "localhost" or "127.0.0.1" using winsock on port 80. I keep getting a 404
> server not found message. I have it set up so it sends out a web page to the
> incoming connections. It has only work on the IP address it finds. I do not
> know of any errors on my machine exept that it is very slow. Maybe its a
> proxy
> thing? I do not have a proxy configured but i think AOL uses them? Or maybe
> it
> a cache thing. I dont know. Maybe ill clear my TEMP and give it another try
> one of these days.
OOOOOHHhhhhhhhhhhhhhhh AOHell, that could be the problem. AOL sets
up a vpn on your puter, connecting *only* to their servers. Try NOT using the
browser that came with AOL, and check the advanced settings in the
connections for the original MS browser that came with your windows. Also,
verify that you have this line in the hosts file in the windows directory (the
hosts file has no .extension) :
127.0.0.1 localhost
AOL does use proxies, but they don't live on your computer, they live on
AOL's machines, to "compress" all the isps they own across the world into a
smaller set of ip addresses. Typically, your real ip as seen by the dialup is
proxied twice before it reaches the real internet, so the ip you are seen with
now may be used by someone in another country tomorrow, at the AOL's
server BOFH's pleasure.
Kat
8. Re: ASYNC SOCKETS
jordah ferguson wrote:
> Do you really think i would ask quote like that if i hadn't tried it a
> couple of times. I used bjacksons hachserv.exw as a simple server then i
> made a telnet look alike to connect to it while offline. It failed. I
> was using the Blocking sockets function WsockCallSocket(). but telnet
> could still connect to it... i know of a couple of guys who have
> experienced such probs....
>From time to time, my winsock gets messed up so I cant open async connection.
Reinstalling DUN files from CD fixes this. But this also affects other apps
(MSIE...)
Maybe the telnet client is broken? (\WINDOWS\telnet.exe that comes with Win98
works
fine for me) Or your OS is completly missing network support? I've just lauched
hackserv.exw, and done 20 telnet connections to it succesfully. Does this work
for you:
(Sorry for Czech version)
<command line>
C:\>ping 127.0.0.1
Odesílá se žádost o ozvìnu poèítaèi hal [127.0.0.1] s 32 bajty dat:
Odezva od 127.0.0.1: bajty=32 èas=1ms TTL=128
Odezva od 127.0.0.1: bajty=32 èas<10ms TTL=128
Odezva od 127.0.0.1: bajty=32 èas<10ms TTL=128
Odezva od 127.0.0.1: bajty=32 èas<10ms TTL=128
Statistika pøíkazu Ping pro 127.0.0.1:
Paketù: Odesláno= 4, Pøijato= 4, Ztraceno= 0 (0% ztráta)
Pøibližná doba od odeslání požadavku do pøíchodu ozvìny v milisekundách:
Nejmenší= 0ms, nejvìtší= 1ms, prùmìrná= 0ms
</command line>
When something is broken, it could look like this:
<cmd line>
C:\>ping localhost
Neznámý hostitel localhost
</cmd line>
-- Martin
9. Re: ASYNC SOCKETS
- Posted by rforno at tutopia.com
May 11, 2002
Kat:
Do you remember my problem connecting to www.giga.com.ar? I did not resolve
it up to today, when you mentioned the HOSTS file. I, mysteriously, had the
wrong address for giga as 200.49.139.144 in HOSTS, instead of 200.49.81.144.
I merely commented out this line and I got to giga without a single problem.
This line was inserted once upon a time by NetCompressor, which after a
while I got rid of.
What is the explanation for all this?
TIA.
----- Original Message -----
From: "Kat" <gertie at PELL.NET>
To: "EUforum" <EUforum at topica.com>
Subject: Re: ASYNC SOCKETS
>
> On 9 May 2002, at 17:44, Robsz2 at aol.com wrote:
>
> >
> > Well I do not have a firewall on my machine and i could not connect to
> > "localhost" or "127.0.0.1" using winsock on port 80. I keep getting a
404
> > server not found message. I have it set up so it sends out a web page
to the
> > incoming connections. It has only work on the IP address it finds. I
do not
> > know of any errors on my machine exept that it is very slow. Maybe its
a proxy
> > thing? I do not have a proxy configured but i think AOL uses them? Or
maybe it
> > a cache thing. I dont know. Maybe ill clear my TEMP and give it
another try
> > one of these days.
>
> OOOOOHHhhhhhhhhhhhhhhh AOHell, that could be the problem. AOL sets
> up a vpn on your puter, connecting *only* to their servers. Try NOT using
the
> browser that came with AOL, and check the advanced settings in the
> connections for the original MS browser that came with your windows. Also,
> verify that you have this line in the hosts file in the windows directory
(the
> hosts file has no .extension) :
>
> 127.0.0.1 localhost
>
>
> AOL does use proxies, but they don't live on your computer, they live on
> AOL's machines, to "compress" all the isps they own across the world into
a
> smaller set of ip addresses. Typically, your real ip as seen by the dialup
is
> proxied twice before it reaches the real internet, so the ip you are seen
with
> now may be used by someone in another country tomorrow, at the AOL's
> server BOFH's pleasure.
>
> Kat
>
>
>
>
10. Re: ASYNC SOCKETS
On 11 May 2002, at 22:16, rforno at tutopia.com wrote:
>
> Kat:
> Do you remember my problem connecting to www.giga.com.ar? I did not
> resolve it up to today, when you mentioned the HOSTS file. I,
> mysteriously, had the wrong address for giga as 200.49.139.144 in HOSTS,
> instead of 200.49.81.144. I merely commented out this line and I got to
> giga without a single problem. This line was inserted once upon a time
> by NetCompressor, which after a while I got rid of. What is the
> explanation for all this? TIA. ----- Original Message ----- From: "Kat"
> <gertie at PELL.NET> To: "EUforum" <EUforum at topica.com> Sent: Thursday, May
> 09, 2002 11:32 PM Subject: Re: ASYNC SOCKETS
>
>
Exactly what I told you!
-- Euler
--
11. Re: ASYNC SOCKETS
On 11 May 2002, at 22:16, rforno at tutopia.com wrote:
>
> Kat:
> Do you remember my problem connecting to www.giga.com.ar? I did not
> resolve it up to today, when you mentioned the HOSTS file. I,
> mysteriously, had the wrong address for giga as 200.49.139.144 in HOSTS,
> instead of 200.49.81.144. I merely commented out this line and I got to
> giga without a single problem. This line was inserted once upon a time
> by NetCompressor, which after a while I got rid of. What is the
> explanation for all this? TIA.
Exactly what I told you!
-- Euler
--
12. Re: ASYNC SOCKETS
On 11 May 2002, at 22:16, rforno at tutopia.com wrote:
>
> Kat:
> Do you remember my problem connecting to www.giga.com.ar? I did not resolve it
> up to today, when you mentioned the HOSTS file. I, mysteriously, had the wrong
> address for giga as 200.49.139.144 in HOSTS, instead of 200.49.81.144. I
> merely
> commented out this line and I got to giga without a single problem. This line
> was inserted once upon a time by NetCompressor, which after a while I got rid
> of. What is the explanation for all this?
I am guessing NetCompressor is a site caching program for your puter, that
operates on 127.0.0.1, and when you cached giga, and then deleted
NetCompressor, the hosts file still pointed to NetCompressor, and since
NetCompressor wasn't there anymore, it wasn't found.
Don't put domains you *want* to reach in hosts if you can avoid it, because
the ip# for domains change occasionally, and you will need to manually
change the hosts file when they do.
Kat
