Note, this is a preliminary spec only. Specifications are subject to change at anytime during the preliminary phase. Final production specs will be announced here.
Questions may be posted in this forum or e-mailed to csc465@bearnotes.com
E-mailed questions and responses may be posted here if it is felt to contribute to the understanding of the specifications or other issues. Names and addresses will be removed before posting.
Protocol Spec v1.2.3: Updated 5-5 @ 12:04pm
Moderator: jaf656s
- Paco103
- Single White Admin
- Posts: 629
- Joined: January 15, 2004, 9:22 pm
- Location: Right Here
- Contact:
Protocol Spec v1.2.3: Updated 5-5 @ 12:04pm
- Attachments
-
- p2p.txt
- Updated 5-5 12:03 PM
Updated specifications
v1.2.3 - (24.8 KiB) Downloaded 391 times
Last edited by Paco103 on May 5, 2005, 11:03 am, edited 9 times in total.
- Paco103
- Single White Admin
- Posts: 629
- Joined: January 15, 2004, 9:22 pm
- Location: Right Here
- Contact:
Specifications have been updated. Most notable changes are that parsing is now done by new lines instead of spaces for almost every occasion, simplifying reading and writing of protocol messages. Also, some updates have been done in the file result messages, most notably by adding the originating regex expression for identification.
- Paco103
- Single White Admin
- Posts: 629
- Joined: January 15, 2004, 9:22 pm
- Location: Right Here
- Contact:
UPDATED:
GET message file length should be the length of the stream the client is requesting. -1 for full file, otherwise the amount of data to send in this stream.
FILE message definition did not match the format/example. Format/examples were correct, message definition left out segment length
PEER message did not define the case in which there are only 2 nodes on the network, so the RQST/JOIN message can not be fulfilled. RQST/JOIN should now be fulfilled with a PEER message as per the protocol, but with no elements in the list
GET message file length should be the length of the stream the client is requesting. -1 for full file, otherwise the amount of data to send in this stream.
FILE message definition did not match the format/example. Format/examples were correct, message definition left out segment length
PEER message did not define the case in which there are only 2 nodes on the network, so the RQST/JOIN message can not be fulfilled. RQST/JOIN should now be fulfilled with a PEER message as per the protocol, but with no elements in the list