Communication protocol
Posted: Sun Dec 06, 2009 10:30 pm
A well chosen software architecture should make the first "communication protocol" not that important. It can easily be modified afterwards. However! These things don't change often once there is a working solution that several people use. So we better get it right from the first time
So I would like to know: Do you prefer a binairy communication protocal (fast and little overhead!) or a human readable CSV- or NMEA-like protocol (easy to read and debug)?
So I would like to know: Do you prefer a binairy communication protocal (fast and little overhead!) or a human readable CSV- or NMEA-like protocol (easy to read and debug)?