consider adding support for the TCP framing method used by the 1.0 OSC spec

[ChrisAshworth]

In the comments of #3, @richardwilliamson notes:

The default setting on Eos for OSC is version 1.0 - which means that the settings have to be changed to communicate over TCP with an eos console, it would be useful if there was an option on the OSCClient to use OSC version 1.0 packets.

The OSC 1.0 spec recommended using a size-count-preamble to send OSC messages over TCP.

It might be nice to allow specifying this as an option.

[richardwilliamson]

I think I've made this work - although I don't seem to be able to do a pull request (see https://github.com/richardwilliamson/F53OSC-RW for my working version - changes are in F53OSCClient, F53OSCParser and F53OSCSocket)

I did a couple of other tweaks as well

[ChrisAshworth]

Cool! Hm, having a pull request for comparison helps a lot to hone in on the specific changes.

Does this page help set one up?

https://help.github.com/articles/creating-a-pull-request-from-a-fork/

[richardwilliamson]

think that's done - I took most of the code from the old commit before 1.0 support was dropped, however for some reason that used 64 bit integers for the size, where they seem to need to be 32 bit, so I changed that.

It seems to work fine for me when talking to an eos, I haven't done a great deal of testing though

[ChrisAshworth]

@balord created branch 17-tcp-osc-1.0-framing for handling TCP non-SLIP framing (OSC 1.0).

Full disclosure — that branch is untested and might not be something we decide to merge. It should be considered experimental for now.