🚀 go-pugleaf

Silly me, after seeing the proposal go by four times you think I would 
save one.  Oh well, from memory:

You talk about "hot" insertion.  How do you go about notifying system
 / application software that the device is now available.  Assuming
you are talking about something a little more sophisticated than DOS
or Windows, you may want to know when a device goes online/offline.

What is the byte order for the address information?  (so much for
no little/big endian issues).

How do tell one device from another?  Will a device always have the
same address no matter what slot is in?  Will the same slot always
the same address (range)?  What happens when I pull out my modem and
insert a hard disk (bye, bye data?).

Obviously, these are mostly software issues, but the hardware needs
to be designed so that the software does not become cumbersome.

If you use this interconnection scheme for loosely linking CPUs:
Above problems with hot insertion, as well as possible security
issues (having one CPU being able to cruise through another
system's memory space is not exactly secure).

Nice idea, but you are not dealing with a DOS (simple, single user,
single tasking) world anymore.  For example, think of the issues
you would have to deal with to remove an active, but flaky modem
module, and insert a good one.  You would have to reinitialize and
have it pick up the data link more or less where you left off.
Again, lots of software issues here, but the hardware needs to 
be able to tell the software:  1) the modem module was pulled,
2)  Another module was installed, 3) it is not the same module,
but is compatible.

Good luck..
					Tim McCaffrey