AnDiXL commented on code in PR #3558:
URL: https://github.com/apache/brpc/pull/3558#discussion_r4116108770


##########
src/brpc/flatbuffers/message.h:
##########
@@ -0,0 +1,166 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements.  See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership.  The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License.  You may obtain a copy of the License at
+//
+//   http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied.  See the License for the
+// specific language governing permissions and limitations
+// under the License.
+
+#ifndef BRPC_FLATBUFFERS_MESSAGE_H
+#define BRPC_FLATBUFFERS_MESSAGE_H
+
+#include "butil/config.h"
+
+#if BRPC_WITH_FLATBUFFERS
+#include <cstddef>
+#include <cstdint>
+#include <utility>
+#include <flatbuffers/flatbuffers.h>
+#include "butil/single_iobuf.h"
+#include "brpc/nonreflectable_message.h"
+
+namespace brpc {
+namespace flatbuffers {
+
+// Space preceding a payload, available to a future RPC transport.
+constexpr uint32_t kDefaultMetaSize = 64;
+// IOBuf slices need not start at an aligned address. The allocator corrects 
it.
+constexpr size_t kBufferAlignment = 64;
+
+class MessageBuilder;
+
+// FlatBufferBuilder cannot recover from a null allocation. Allocation failure
+// and sizes outside FlatBuffers' offset range are fatal, even in release 
builds.
+class SlabAllocator : public ::flatbuffers::Allocator {
+public:
+    SlabAllocator() : _data(nullptr), _capacity(0) {}
+    SlabAllocator(const SlabAllocator&) = delete;
+    SlabAllocator& operator=(const SlabAllocator&) = delete;
+    SlabAllocator(SlabAllocator&& other) noexcept : SlabAllocator() {
+        swap(other);
+    }
+    SlabAllocator& operator=(SlabAllocator&& other) noexcept;
+
+    uint8_t* allocate(size_t size) override;
+    void deallocate(uint8_t* p, size_t size) override;
+    uint8_t* reallocate_downward(uint8_t* old_p, size_t old_size,
+                                size_t new_size, size_t in_use_back,
+                                size_t in_use_front) override;
+    void swap(SlabAllocator& other) noexcept;
+
+private:
+    butil::SingleIOBuf _iobuf;
+    uint8_t* _data;
+    size_t _capacity;
+    friend class MessageBuilder;
+};
+
+// Construct the allocator before the FlatBufferBuilder base uses it, and
+// destroy it after that base has returned its buffer.
+struct SlabAllocatorMember {
+    SlabAllocator slab_allocator_;
+};
+
+// A move-only message. Parsing checks framing, not the schema: Verify<T>()
+// must succeed before reading data received from an untrusted peer.
+class Message : public NonreflectableMessage<Message> {
+public:
+    Message() : _meta_size(0), _msg_size(0) {}
+    Message(const Message&) = delete;
+    Message& operator=(const Message&) = delete;

Review Comment:
   Updated all four reviewed types in `78bdef66`: `Message`, 
`ServiceDescriptor`, `RpcChannel`, and `Service` now use 
`DISALLOW_COPY_AND_ASSIGN`, with an explicit `butil/macros.h` include rather 
than relying on transitive headers.
   
   The final code was rebuilt and tested with macOS CMake/Make and Linux 
CMake/Make/Bazel; the 22 message and 33 protocol cases passed with no failures 
or skips, and generated-service codegen tests also passed.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to