Owen Brotherwood 30211aa006 Correction for max. length of advertised url to 17
https://github.com/google/eddystone/tree/master/eddystone-url#frame-specification states 1-17
When one makes a general google for the max length, some have written 18 and some 17 :(
The difference could lie in the https://github.com/google/eddystone/tree/master/eddystone-url#url-scheme-prefix which adds an extra byte but it's use is to in someway allow for more bytes in the 1-17.
The implementation in the micro:bit Lancaster is unknown as to how the url-scheme-prefix is or is not used: there does not seem to be a scheme for "Just take the 1-17" for the url.

At the moment, "play it safe" and write 17 ?
2016-12-06 20:51:44 +01:00
..
2016-09-01 06:49:39 -07:00
2016-10-28 08:34:04 -07:00
2016-11-01 17:44:37 -07:00
2016-11-01 17:44:37 -07:00
2016-11-10 08:37:13 -08:00
2016-12-01 18:35:10 -08:00
2016-10-24 16:58:12 +01:00
2016-11-29 00:04:21 -08:00
2016-11-01 21:48:11 -07:00
2016-08-30 13:34:05 -07:00
2016-07-14 12:09:40 -07:00
2016-11-01 17:44:37 -07:00
2016-11-11 15:14:54 -08:00
2016-11-01 17:44:37 -07:00
2016-11-01 21:48:11 -07:00
2016-08-17 09:44:15 -07:00
2016-11-01 17:44:37 -07:00
2016-11-11 06:54:17 -08:00
2016-11-01 21:48:11 -07:00
2016-11-01 17:44:37 -07:00
2016-11-01 21:48:11 -07:00
2016-11-01 17:44:37 -07:00