1. RE: ASYNC SOCKETS
So do you know the reason why or should we attack Jesus & Greg. or some
Winsock Coders like Kat, Thomas
hehe
jordah
Does any one know how i can use Async Sockets. I'm making a Telnet
Client
Robsz2 at aol.com wrote:
>
>
> --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.
>
>
2. RE: ASYNC SOCKETS
Well, i'm writing a telnet client. the reason i hate sync sockets they
tend to freeze the proggy till they have done their work. Also in my
email client when downloading large emails the prog tends to freeze. The
only soln i did was placing doEvents in the inner loop of
WsockReadData()
Anyway, i need help on how you setup a async connection ie
when you click a btn it gets server information from sles and connects,
interacts with the server ... thats all
Thanx Rob
Robsz2 at aol.com wrote:
> 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.
>
>
3. RE: ASYNC SOCKETS
I'm pretty sure most every system has an echo server built with the
sockets just for such a reason, for testing. port 7??
It's often exploited as a hole for hackers to enter systems.
Chris
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.
>
> Martin
>
>
4. RE: ASYNC SOCKETS
Martin,
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....
its a shame you can't test clients programmed using winsock.ew while
offline?
jordah ferguson
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.
>
> Martin
>
>
