[Coco] becker and VCC1.43beta, now DW4

[Gene Heskett]

On Sunday 21 April 2013 09:47:30 Gene Heskett did opine:

> On Sunday 21 April 2013 07:51:45 Aaron Wolfe did opine:
> > On Sat, Apr 20, 2013 at 4:46 AM, Bob Devries <devries.bob at gmail.com>
> 
> wrote:
> > > Now, if I wanted to use a *different* computer to run VCC, would I
> > > change the IP number from 127.0.0.1 to whatever the client computer
> > > is, e.g. 192.168.1.4 in both DW4 and VCC?
> > 
> > No... you would only change the IP address in VCC.
> > 
> > I've added a diagram to the Ports documentation in the DW4 wiki. Maybe
> > it will help clear things up?
> > 
> > https://sourceforge.net/apps/mediawiki/drivewireserver/index.php?title
> > =U sing_DriveWire#Ports
> 
> Even after reading that, which does help, I am still not enlightened
> enough to be able to setup that basic09 web server, so that (and I'd
> have to setup a NAT rule in my router too) someone could send their
> browser to my web page, but change the port number to say 6309, and
> actually be accessing the coco.  I can take care of the NATing and
> routing, but how would DW be setup, and inetd on the coco be configured
> to accomplish this?
> 
> I'd also need to grab a copy of that basic09 web server, where is that
> downloadable?  Or do I already have it as part of the DW install? I am
> not seeing anything like it that I recognize, which I assume is
> something like httpd.b09. This lists corpus should contain that info,
> but searching the last 11 years of it comes up empty.  And I do not see
> it in the 3rdparty/packages/basic09 tree of my repo either.  I think
> its safe to say that unless its on my web pages, I don't have it.  And
> its not visible there.

addendum: Running the latest server, as of late last night, I used minted 
from the coco's console to add the starting of 2 additional shells on z1 
and z2 to the startup, and reset it.  They look great on my linux screen.

BUT, dw on the coco is busier than a one armed paper hanger according to 
the leds on the serial-usb adapter.

Should that be the case when neither screen is actually doing anything?
Its as if it is continuously refreshing the screens.  The coco seems to be 
a bit loaded, not quite as snappy as normal.

The server tab says there are just under 1000 operations a second.  
Floating in the 940's range.

That doesn't seem normal.

> > I think maybe you're not understanding that the server IP and port the
> > UI uses to talk to the server is an entirely different thing than the
> > server IP and port that VCC uses to talk to an instance on the server.
> > 
> >  They will never be the same, as they are different processes
> > 
> > entirely.  If you're doing everything on one computer they will both
> > use localhost or 127.0.0.1 as the server IP, but the ports will always
> > be different.
> > 
> > You could run all three parts on different computers.  For instance,
> > maybe you want to run the server on a tiny Raspberry Pi with address
> > 192.168.1.10, the UI on your Windows computer with address
> > 192.168.1.20, and VCC on another machine with address 192.168.1.30.
> > In this case, the UI would have a server setting of 192.168.1.10 port
> > 6800, and VCC would have a server setting of 192.168.1.10 port 65504.
> > The DriveWire server itself doesn't need to know any of the client's
> > addresses in any case.
> > 
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> 
> Cheers, Gene


Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
My views 
<http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml>
You dialed 5483.
A pen in the hand of this president is far more
dangerous than a gun in the hands of 200 million
          law-abiding citizens.