Bug / Feature #211
closed
Added by spale over 13 years ago.
Updated over 11 years ago.
Start date:
09 November 2010
Request Type:
Feature Request
Affected Users:
Developers
Description
I'd like to implement a client. Therefore I request the source code of the current client and server implementations and the documentation of the client-server protocol.
Yes Philipp, but how so I SVN on this?
The documentation isn't progressed that far mostly because the protocol or rather the message/containers used are quite complex.
- Category set to Documentation
- Status changed from New to 2
- Assignee set to Exception
- % Done changed from 0 to 50
A version of the Pi-Vote Protocol documentation can now be found in the files section.
I had a quick look at the doc are something 'popped up' in front of my eyes. In point 1.2 "Example", I see length and data. Length is an int32 host encoded, not in network byte order. Is this a mistake or done on purpose? RFC791 (IPv4) is pretty clear about this: "The order of transmission of the header and data described in this document is resolved to the octet level. Whenever a diagram shows a group of octets, the order of transmission of those octets is the normal order in which they are read in English.", meaning most significant octet is 'left' and less significant octet is 'right'.
http://en.wikipedia.org/wiki/Endianness#Endianness_in_networking
- Tracker changed from 3 to Bug / Feature
- Status changed from 2 to Needs Work
- Status changed from Needs Work to Done
- Target version set to N/A
- Request Type set to Feature Request
- Affected Program set to None
- Affected Users set to Developers
Standing tasks will no longer be handled as ticket.
- Status changed from Done to Closed
Automatically closed after 30 days
Also available in: Atom
PDF