Re: [WWWOFFLE-Win32] wwwoffle through network is so sloowwww

[JPT]

> "Andrew M. Bishop" <[EMAIL PROTECTED]> wrote:
> > WWWOFFLE does do a name lookup after the IP address has been found.
> > This is not normally a problem since UNIX systems tend to have DNS
> > working for hosts that are local and likely to connect.
> >
> > On Win95 there was a file called c:\windows\hosts that was the same
> > format as the UNIX hosts file.
> >
> > 192.168.0.1     thishost
> > 192.168.0.2     thathost
> >
>
> Thank you!!! It works now.
> Could you please add this to README.win32?

No. It does not work. Now even Opera on Localhost is slow / cannot read
pages properly. IE on Localhost still works.

Yesterday I got much of these messages:

wwwoffled[1128](Information): Child wwwoffles exited with status 1
(pid=1368).
wwwoffled[1128](Information): Child wwwoffles exited with status 0
(pid=1344).
wwwoffled[1128](Information): HTTP Proxy connection from host RET
(192.168.0.12).
wwwoffles[1200](Warning): Could not parse HTTP request (Empty request).

Today, there were even return codes of 3 and 4:

wwwoffles[1248](Information): No more outgoing requests.
wwwoffled[1112](Information): Child wwwoffles exited with status 3
(pid=1148).
wwwoffled[1112](Information): Child wwwoffles exited with status 3
(pid=1248).
wwwoffles[480](Information): Cache Access Status='New Page'.
wwwoffles[308](Information): Cache Access Status='New Page'.
wwwoffled[1112](Information): Child wwwoffles exited with status 0
(pid=308).
wwwoffled[1112](Information): Child wwwoffles exited with status 4
(pid=480).

Do the messages indicate serious problems? Or is this normal behavior?


winnt\hosts now is on both systems:
127.0.0.1       localhost
192.168.0.10    jpt  # wwwoffle
192.168.0.12    ret

Jan