Basic ideas for protocol addded

diff --git a/.gitattributes b/.gitattributes
index accc628e172cbe3b5ca8a7cd357ec5d029db019f..2cc9bac176332b33203ed75b39e550002b09e919 100644 (file)
--- a/.gitattributes
+++ b/.gitattributes
@@ -41,3 +41,4 @@ mindmaps/Generic[!!-~]Object[!!-~]Sharing[!!-~]Protocol.mm -text
 misc/possible_hub_states.txt -text
 protocol-drafts/Generic[!!-~]Object[!!-~]Sharing[!!-~]Prototocol[!!-~]0.0.1.odt -text
 protocol-drafts/Generic[!!-~]Object[!!-~]Sharing[!!-~]Prototocol[!!-~]0.0.1.pdf -text
+protocol-drafts/protocol-ideas.txt -text

diff --git a/protocol-drafts/protocol-ideas.txt b/protocol-drafts/protocol-ideas.txt
new file mode 100755 (executable)
index 0000000..8bb1abc
--- /dev/null
+++ b/protocol-drafts/protocol-ideas.txt
@@ -0,0 +1,27 @@
+Ideas for the Generic Object Sharing Protocol
+=============================================
+
+Created: 2009-08-12, 12:38am
+Updated: xxxx-xx-xx, xx:xx
+Author: Roland Haeder
+
+--------------------------------------------------
+
+Package-level:
+--------------
+- base64-encoded to reduce/prevent transmission errors
+- with decorators there is no problem in transparent encryption
+- not all peers needs encryption enabled because they announce it to other peers
+- the peers then can remember wether encryption is enabled
+- messages/objects are sent in different frames
+- a frame has a head containing fields and a body seperated with markers from it
+- fields are name/value pairs seperated with markers from each other
+- the body contains the transfered message/object
+- a flag in the header indicates wether the body is encrypted
+- how the key is being transfered needs to be evaluated
+
+Fields for a network frame:
+---------------------------
+
+Message-level:
+--------------