If you build something yourself (which would obviously then
meet the "maintainability" requirements), you could throw
Well, I am not going to make the radio modules myself (no way can I meet
type approval, even if I meet the technical specs), but I would certainly
consider making something _round_ said modules.
in some reasonable buffering. 128MB SDRAM is dirt
cheap
(?1 or so) and that is likely to be enough buffering
for almost any classic machine. So even if your radio chip
Now that's something that had not really struck me (which is why this sort
of discussion on the list is so useful) -- that the file sizes I am going
to be transfering _are_ limited. 128Mbytes is larger than the available
mass storage (let alone RAM memory) on most of my classics, so except in
very unusual ciercumstances, the data I wish to transfer is going to be a
lot smaller than that. Which means a buffer is certainly an option.
wants to pause for breath, your classic computer
doesn't
need to know.
Basically this is a (bidirectional) print buffer with
a radio welded on the end.
Does it need to be idriectional? A buffer between the classic machine
output and the radio module input should be enough. But I suppose if I
put one in the other way too, I can use it to do effectively baud rate or
data format conversions.
Of course I can output a 'buffer getting full' signal to those classic
machines that accept hardware flow control, the others will proably not
eend enopuug h data all that fast to need it.
-tony