Fumbling through network programming

Last year I spent a good portion of September figuring out how to get my phones to communicate to each other in that Bluetooth/GPS Windows Phone app I was writing.

I guess what really steered me towards Bluetooth was my aversion to communicating through the web. Bluetooth would help keep things somewhat local and would simplify my application by cutting out the need for a server to forward information to the host phones. I also had bad memories from that one year when my group and I spent the Thanksgiving Holidays implementing our Senior Design project. Somehow I couldn’t get a good grasp on socket programming, so I ended up proposing that we just use libpcap to sniff and inject instead of actually writing a robust routing system.  I suppose our implementation was robust enough in the interim,as a proof of concept, but production would be much different. When things started going South over Thanksgiving, we turned to our friends at the ACM in Siebel Center, only to get a door slammed in our faces, no joke. Oh well, the project worked alright. Even so, I kind of just decided socket programming wasn’t going to be a part of my life after that.

Anyway while doing that Windows Phone app, I spent a ton of time designing a somehow functional communications protocol and even a three way handshake to make sure things were being sent and received. Kind of cool considering I’m finally learning about this stuff at school again. Honestly should’ve picked up a book back then. Probably would’ve saved me a month. This time around everything’s much easier.

Rest in peace (pieces) PartyTracker. The logo and icon were the slickest part of the entire program. 😛