Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The goal of this library is to provide the familiar sockets interface over a non-traditional eth, in this case sound.

Can you expand on your question? I think I understand what you're saying but I don't quite see what it would accomplish.

And this is an "actual" modem, whatever that means. If you mean an IETF/RFC modem spec, there are many reasons. Those specs are focused on narrowband POTS limitations, which we don't face over a less-restricted channel. Implementing those features might be interesting from a vintage perspective but would require substantial work to achieve compatibility for relatively little gain.



If you did it as a traditional modem then one could hook up any old piece of software to the appropriate character devices and you'd be off to the races. Not everything is sockets, and there are simple and relatively easy to use wrappers around a standardized serial character interface to turn such a connection into one supporting all of the regular internet protocols. It seems - but I may be wrong about this - that this solved something at a different layer than what I would have expected.


Ah, yeah, that makes sense. My plans for this library are mostly focused on using the sockets directly, with the library linked by both peers. I'm really interested in being able to use this as a simple UDP client/server.


You'd get that just about for free by running SLIP or PPP over your audio modem.


Perhaps - my plan is to use this on iOS and Android where I suspect SLIP and PPP interop is not as straightforward. By bundling everything in with the app, there won't be any kernel dependencies, aside from the sound card.


   > over a non-traditional eth,
   > in this case sound
Sound is a non-traditional way of moving data?!


Non-traditional in the sense that I can't immediately transport data over my sound card with <sys/socket.h>


If you install a software modem ... you can?


Mouth sounds.



Thanks for posting that! :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: