Content deleted Content added
AdaHephais (talk | contribs) Internal link Tags: Visual edit Mobile edit Mobile web edit Advanced mobile edit |
AdaHephais (talk | contribs) Internal link Tags: Visual edit Mobile edit Mobile web edit Advanced mobile edit |
||
Line 102:
== Design ==
OSC messages consist of an address pattern (such as <code>/oscillator/4/frequency</code>), a type tag string (such as <code>,fi</code> for a [[float32]] argument followed by an [[int32]] argument), and the arguments themselves (which may include a time tag).<ref name=":1" /> Address patterns form a [[Namespace|hierarchical name space]], reminiscent of a [[Unix]] [[filesystem]] path, or a [[Uniform Resource Locator|URL]], and refer to "[[Method (computer programming)|Methods]]" inside the server, which are invoked with the attached [[Parameter (computer programming)|arguments]]. Type tag strings are a compact string representation of the argument types. Arguments are represented in binary form with four-byte alignment. The core types supported are
* 32-bit [[two's complement]] signed integers
| |||