syncbase: use byte[] for range start/limit in wire API

VDL assumes strings are utf-8, but start and limit are not guaranteed to be
valid utf-8 strings. For example, when using byte-based key ordering (the
default), prefix->range conversion may produce a 'limit' value that ends with a
byte that's not valid utf-8.

Change-Id: I5ff5f29718d76717a21a54a63f998e07224084dc
1 file changed
tree: 8c5b451764e3481f8c84922f6084d74b6cd92749
  1. services/