Somewhat of an issue with passing arbitrary binary data is that we are dealing with JSON, which will require conversion to escaped ASCII anyway (or some odd B64 solution).
The OCRepresentation changes for a new type (uint8_t) are pretty trivial, however the JSON serialization will require quite a bit of mangling. On Tue, 2015-04-28 at 11:04 -0700, Thiago Macieira wrote: > On Tuesday 28 April 2015 16:45:28 Keane, Erich wrote: > > The thought here is that std::string is already a collection of 'char', > > and a single-length string is a single char. > > > > I'm curious to see what others have to say, so perhaps this is something > > that could be added anyway. > > > > If you push a review to Gerrit, I'd definitely be willing to review and > > consider it. > > std::string should be left for text and we should use std::vector<uint8_t> > for > binary data. > > If we were in the Qt world, we'd have QString and QByteArray. For IoTivity, I > don't think we should use anything but US-ASCII and UTF-8 for text, so we > don't need the wider character types. >
