Seebs 79940cf077 encoding/proto: allow distinct serializers ... We want to be able to control whether or not we use roaring to serialize Rows, which means serializers have to be able to be distinct. We also make corresponding changes to http/handler.go to have it use the exported serializers directly rather than the API's serializer (which is always the base protobuf serializer right now, and if it weren't, that would be bad because we were assuming it was). When we're accepting protobuf from a pilosa server, flag that we'll accept roaring bitmaps as opposed to the naive column representation.		2020-05-15 16:22:08 -05:00
..
proto.go	encoding/proto: allow distinct serializers	2020-05-15 16:22:08 -05:00