Ideas for RCP 2.0

[i-n-g-o]

• ~rework of id to allow a bigger range and save bits (encode the format of the id within the id-bytes)~
• ~try to avoid terminators~
• ~remove language strings~ (decided to leave them as they are)
  • until now: each client can choose the language individually without the need of a special server
  • this change would imply that each client needs to request a language on initialize
  • reason: it seems not a good idea to transmit more than one language
• ~remove timestamp from packet~ (we leave timestamps because it seems handy to have)
• ~type enum: send index instead of string~ (note: deal with reordered lists outside if protocol)
• ~type string: automatically use tiny,short,long string for string values~
  • ~consider to remove long-strings as this type does not seem to be useful~ (transmitting up to 4.2GB of data)
• specify Layout
• specify Style (?)

[joreg]

from the above consider to bring to 1.0

• ~remove language strings~ -> decided not too because the two arguments (more complex implementation, and saving bandwidth) seem neglectible
  • related, we thought of adding a translation-key to parameters and an idea of translation tables...
• ~type enum: send index instead of string~ -> agreed
• ~remove idea of long-string and then only have short and long strings~ -> agreed
• ~make string parameter a long string~ -> agreed
• ~remove "scale" from number definition~ -> agreed

[i-n-g-o]

I added #30 for all open issues related to 1.0