When I opened the message, I found that Bernie Cosell had written:
> > Problem is I can't acces the PopFile interface to see what's there
> > and if the messages are being classified correctly.
> When it isn't answering its UI, it isn't running. Just kill it and
> restart it.
I should have said I can't access it via IE. That's what called my
attention to IE's problem. I just accessed it via Mozilla.
Killing it and restarting it, doesn't do the job.
> > I get "connection refused". Well, the connection is my own
> > computer. So it must be an "inside job" <smile>.
> Correct -- it is running a mini-web-server listening on a local socket
> and if it gets hung/confused, it stops listening and at that point your
> browser can't connect.
> > Any ideas about why I can't even access "local host"?
>
> You can -- what you're not understanding is that with TPC you don't
> access a 'host' but always a "host/port" pair.
You are correct about me not understanding exactly how it works.
I do know it's all within my computer.
In order to be able to
> connect, the particular host must have a server listening on the specific
> port you're trying to connect to. In my case, for example, I moved
> popfile to port 9000, so I connect to "localhost:9000". You probably
> connect to "localhost:8080". In either case, the error message isn't
> telling you that the *HOST* has a problem, but only that you can't
> connect the particular _port_ you're trying to connect to.
And why might that be? And how do I move it to another port as
you did?
Would IE have a problem with 8080 and not Mozilla?
Thanks,
Jim
--
----------------------------------------
To unsubscribe, mailto: [EMAIL PROTECTED]
Is your picture included in the Official Win-Home List Members Profiles Page?
http://www.besteffort.com/winhome/Profiles.html
If not, write to: [EMAIL PROTECTED]
