Marauroa 3.9: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Hendrik Brummermann No edit summary |
imported>Kymara wikilink Marauroa once |
||
| (34 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
{{Navigation for Marauroa General}} |
{{Navigation for Marauroa General}} |
||
| ⚫ | |||
<div style="border:2px solid #A00; background-color:#FFA; padding:1em">'''This article deals with a pre release version of Marauroa.</div> |
|||
| ⚫ | |||
Please note, the term "Marauroa users" refers to developers using Marauroa in their own software. It does not refer to the end user of the programs developed using Marauroa. |
Please note, the term "Marauroa users" refers to developers using Marauroa in their own software. It does not refer to the end user of the programs developed using Marauroa. |
||
| Line 11: | Line 8: | ||
== Version compatibility == |
== Version compatibility == |
||
Marauroa 3.9 introduces protocol version 34, but is fully compatible to older protocol versions back to 31 on both the server and the client side. A server can handle clients of different versions (both older and newer than the server) at the same time and will use the appropriate feature set for each of them, |
Marauroa 3.9 introduces [[Marauroa_Glossary#P|protocol version]] 34, but is fully compatible to older protocol versions back to 31 on both the server and the client side. A server can handle clients of different versions (both older and newer than the server) at the same time and will use the appropriate feature set for each of them, |
||
== Content Transfer includes hash == |
== Content Transfer includes hash == |
||
| Line 37: | Line 34: | ||
; Reason for change : This change reduces the amount of network traffic; especially for very short turn times (e. g. Marboard uses 10ms in order to be very responsive) |
; Reason for change : This change reduces the amount of network traffic; especially for very short turn times (e. g. Marboard uses 10ms in order to be very responsive) |
||
; Impact on Marauroa users : None, yet. Starting with the future Marauroa 4.0 empty perceptions will actually be omitted. There might be an impact, if a client assumes that it receives a perception per turn time interval. |
; Impact on Marauroa users : None, yet. Starting with the future Marauroa 4.0 empty perceptions will actually be omitted. There might be an impact, if a client assumes that it receives a perception per turn time interval. |
||
; Details : The client was counting the perceptions in order to determine when to send the "keep |
; Details : The client was counting the perceptions in order to determine when to send the "keep alive" message. Starting with 3.9, the client will send the "keep alive" message based on actual passed time. Note: The server will not yet omit empty perceptions in version 3.9, but will start to do that in version 4.0 for 3.9 and above clients. The reason for this approach is that the server side changes are a lot simpler in the refactored code. |
||
== RPClass support for RPAction == |
== RPClass support for RPAction == |
||