UPDATE #2 : VOS markup language for service delivery between nodes is working, right alongside HTML requests. Architecture transmits VOSML as JSON embedded data inside the "script" tags. Looks fantastic. Screenshots soon.
UPDATE : Ported the code from Turbo C++ 3.0 to Open Watcom 1.9 and now have the same code base compiling and running under DOS16, DOS32 and Windows XP/2000/NT environments. Platform independent web server and platform independent browser, platform independent I2C and platform independent Parallel Port controllers. Runs with or without LAN connected, supports PPP, SLIP and Modem driven network connections. Also found a way to support Novell Client32 in DOS with ODI packet driver using same code base. If you can't find a packet driver for your Ethernet card, almost all manufacturers are still making ODI drivers for DOS to support Novell networks. Virtual web directories of services, interface controllers, information and archives with standard .CSS and HTML layouts. No frames or support beyond HTML 3.0, may soon support AJAX style constructs in ECMAScript for better refreshing of real-time data. Had this running in 384K MS-DOS and FreeDOS in 16 bit real mode.
All I can tell you is, it's going to be more than most people could've possibly imagined anyone could get running on an 8086/8088 device. I can assure you, it will blow your mind. You will wonder how I crammed so much into so little.
It's now at 114K for the DOS 16-bit exe. It's so tiny it will run on very small x86 compatible devices, including DOS Stamp, Flash EX-86, etc.
Here's what this tiny program does ...
1. Provides customizable, configurable control and scheduling of all devices on an I2C line and a Parallel Port. Simple .INI files and a VOS BASIC interpreter provide all scripting functions.
2. Is a real-time web server over HTTP allowing anyone with a browser to control the installation remotely. Any browser supporting timer refresh will be viewing and operating on real-time data. I've tried it with the Arachne browser (for DOS) and the built-in browser inside one of my thin clients, worked flawlessly with both of them.
3. Delivers up a virtual directory of web services that can be customized for each shelter in which it runs. Provides an index page for all services just like a real web server if no link specified.
4. Any x86 device can be customized to handle the area of the shelter it manages and will plug seamlessly into the total VOS system once it is running. You can have one manage your generator room, another for your inventory system, another box running your environmental control or hydroponics lab. It is the same program configured differently for each setting.
I know, you don't believe it. Wait until you see it. I've spent a lot of time coding this thing and have thrown out about 100,000 lines looking for the perfect paradigm to sit at the base of the VOS networked system. I got it. This is it.