10 Feb 03:32
the pervasiveness of TPDD protocol
Furthermore, it seems that since TPDD protocol will work well over wide area, and is by nature unable to overflow the RX buffers on the M100, then it could be further expanded like was done by TS (the desklink extensions), to support * terminal sessions * file downloads within terminal And, since we are likely to use terminal to run web apps, then we have a generalized solution for bi-directional data transfer with the M100. So, I guess my proposal is to further expand TPDD protocol to handle other forms of data transfer, so it is the underlying transport protocol for data to and from the wide-area network gateway. ..Steve On Tue, Feb 9, 2010 at 8:36 PM, Stephen Adolph <twospruces@...> wrote:> I've been thinking about bluetooth and the M100. It seems to me that > the best "achitecture" for mobile net enabled apps would be as > follows- > > 1) M100 with an RS-232 bluetooth dongle (hardware flow control!), and > REX of course. > 2) a smartphone, with WiFi support > 3) optional - a NADSbox with an RS-232 bluetooth dongle > 4) a better terminal program for M100, as an option ROM, including XMODEM > > It is easy to instruct bluetooth to connect to either NADSbox or > smartphone.. This can be scripted basically. We know that TPDD > protocol runs well on bluetooth now. Also, a version of Desklink > could be made for Blackberry. > > Then, all we are doing is writing apps for Blackberry, to adapt text > email, bulletin board, downloads etc. > > I think this would do it all, and avoid any further custom hardware. > The Blackberry and NADSbox can sit out of sight, and all you'd need is > an RS-232 Bluetooth dongle on the M100. >
RSS Feed