Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Slashdot Deals: Deal of the Day - Pay What You Want for the Learn to Code Bundle, includes AngularJS, Python, HTML5, Ruby, and more. ×

Submission + - Designing a Network Protocol (drdobbs.com) 1

CowboyRobot writes: When requirements are tight and unforgiving, it's sometimes easier to design your own protocol. The article describes the design considerations for a basic network architecture that could be used as a starting point for a simplified personal area network. This particular network consists of low-power nodes that capture physiological data from sensors and condition it before sending it to a central node for processing. The design considerations include: Does each node need to communicate outside of the closed system? What happens if the communication link for a node is down? Is it catastrophic if a single data sample is lost? Does the data reception need to be acknowledged by the receiver?
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Designing a Network Protocol

Comments Filter:
  • If you're actually capable of creating a new network protocol, you never need to ask whether or not you should, you'll already know when to do it.

    And consequently, if you ever need to ask if you should create a new network protocol, the answer is invariably NO.

"When it comes to humility, I'm the greatest." -- Bullwinkle Moose