Strip down message size for MessageBridgeServer
This makes it much much less costly to have a pool of messages we use
for receiving data into on the server side. The server only really
receives the connection message along with any remote timestamps being
sent back.
While we are here, make sure the sha256 is the right length... We were
blindly treating it as a string, and that causes it to overflow the
destination buffer.
Change-Id: Id4bfa0d1d9c25e0beead39248f32b361b722059d
Signed-off-by: Austin Schuh <austin.schuh@bluerivertech.com>
diff --git a/aos/network/message_bridge_protocol.cc b/aos/network/message_bridge_protocol.cc
index a0c68d4..38e16b2 100644
--- a/aos/network/message_bridge_protocol.cc
+++ b/aos/network/message_bridge_protocol.cc
@@ -34,11 +34,16 @@
if (connection->name()->string_view() == node_name &&
channel->source_node()->string_view() == remote_name) {
// Remove the schema to save some space on the wire.
- aos::FlatbufferDetachedBuffer<Channel> cleaned_channel =
- RecursiveCopyFlatBuffer<Channel>(channel);
- cleaned_channel.mutable_message()->clear_schema();
- channel_offsets.emplace_back(
- CopyFlatBuffer<Channel>(&cleaned_channel.message(), &fbb));
+ flatbuffers::Offset<flatbuffers::String> name_offset =
+ fbb.CreateSharedString(channel->name()->string_view());
+ flatbuffers::Offset<flatbuffers::String> type_offset =
+ fbb.CreateSharedString(channel->type()->string_view());
+
+ // We only really care about name, type, and max size.
+ Channel::Builder channel_builder(fbb);
+ channel_builder.add_name(name_offset);
+ channel_builder.add_type(type_offset);
+ channel_offsets.emplace_back(channel_builder.Finish());
}
}
}