1 Ideas for the Generic Object Sharing Protocol
2 =============================================
4 Created: 2009-08-12, 12:38am
5 Updated: xxxx-xx-xx, xx:xx
8 --------------------------------------------------
12 - base64-encoded to reduce/prevent transmission errors
13 - with decorators there is no problem in transparent encryption
14 - not all peers needs encryption enabled because they announce it to other peers
15 - the peers then can remember wether encryption is enabled
16 - messages/objects are sent in different frames
17 - a frame has a head containing fields and a body seperated with markers from it
18 - fields are name/value pairs seperated with markers from each other
19 - the body contains the transfered message/object
20 - a flag in the header indicates wether the body is encrypted
21 - how the key is being transfered needs to be evaluated
23 Fields for a network frame:
24 ---------------------------
28 - a message is only identified by itself (the body)
29 - the header does not contain any message-specific parts
30 - a message may contain extra data e.g. hash trees for larger object but no ibjects
31 - therefor its total size is limited in opposite to an object
32 - extra data is seperated by a marker from the message
33 - an end-marker closes the whole message