Print
Listen
By 
Click to enlarge image
Subscribe to our Newsletters
O'Reilly on YouTube
O'Reilly on Twitter
O'Reilly on Facebook
Watering Hole Feed
©2009, O'Reilly Media, Inc. (707) 827-7000 / (800) 998-9938 All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. |
About O'Reilly
Academic Solutions Authors Contacts Customer Service Jobs Newsletters O'Reilly Labs Press Room Privacy Policy RSS Feeds Terms of Service User Groups Writing for O'Reilly |
Content Archive Business Technology Computer Technology Microsoft Mobile Network Operating System Digital Photography Programming Software Web Web Design |
More O'Reilly Sites
O'Reilly Radar Ignite Tools of Change for Publishing Digital Media Inside iPhone O'Reilly FYI makezine.com craftzine.com hackszine.com perl.com xml.com Partner Sites InsideRIA java.net O'Reilly Insights on Forbes.com |
300 baud as 1960's tech?
Pleeeeeezzze!
The 1960's were for 110 baud (10 bytes/second, 11 bits/byte, used an extra parity bit). Or less I remember moving up to 300 baud in the the 1970's. What an improvement. Why, it was just faster than you could read! (Remember, these were the days of text based terminals.)
In the late 1980's i worked for a company that still made
Theoretically you could use morse code, if the entire syntax fits into the morse alphabet. Heck, modern network traffic still uses the very same technology but binary.
Heck, just view the page source and transmit that. both Morse and semaphore should be able to handle such, and those sailors will get the page in less than a week...two days at most.