[Coco] Using DriveWire to write network software

[Mark D. Overholser]

On 29-Mar-17 10:45, Brett Gordon wrote:
> On Mar 29, 2017 12:41 PM, "Mark D. Overholser" <
>>
>> DriveWire is a Possible Network Transport, so is the Lantronix, UDS-10s
> also the CoCoNIC in development or even another Networking option,
> including Wireless...   ( ESP 8266 WiFi Modules )
>>
>
> DW works well as a layer 2 transport.  I have extended william astle's 'lw
> wire' server to accept eth0 frames, and use it as an endpoint for fuzix's
> native stack.  And this all works fine for gary's fpg, and emulators (mess
> and vcc) - all support dw, allowing for inet on all my cocos.
>

Layer 2, That is what I have surmised from the Conversations, without 
looking into the Code ( or Documentation )


I have a question, about the CoCo Client using the Bit-Banging Port..

Because of the High Overhead of Reading the Bit-Banged Serial, I 
"assume" that the DriveWire Server is completely "driven" by the CoCo 
Client???

Because the CoCo needs to be Ready to Receive any Data sent from the 
Server, and it seems like you would Only want to Receive Data when it 
was Requested..  Not at the Servers "whim"


> I like John Linville's idea of doing dw over  ethernet.  That'll probably
> be my RetroChallenge this April.
>

That would be fantastic....  Two DriveWire Servers could "communicate".. 
  Making your Disk Image, Local or Remote...


> Brett
>


MarkO