mirror of
https://github.com/RGBCube/serenity
synced 2025-10-31 21:52:45 +00:00
85a84b0794
Classes reading and writing to the data heap would communicate directly with the Heap object, and transfer ByteBuffers back and forth with it. This makes things like caching and locking hard. Therefore all data persistence activity will be funneled through a Serializer object which in turn submits it to the Heap. Introducing this unfortunately resulted in a huge amount of churn, in which a number of smaller refactorings got caught up as well.
28 lines
563 B
C++
28 lines
563 B
C++
/*
|
|
* Copyright (c) 2021, Jan de Visser <jan@de-visser.net>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <LibSQL/Serializer.h>
|
|
|
|
namespace SQL {
|
|
|
|
void Serializer::serialize(String const& text)
|
|
{
|
|
serialize<u32>((u32)text.length());
|
|
if (!text.is_empty())
|
|
write((u8 const*)text.characters(), text.length());
|
|
}
|
|
|
|
void Serializer::deserialize_to(String& text)
|
|
{
|
|
auto length = deserialize<u32>();
|
|
if (length > 0) {
|
|
text = String(reinterpret_cast<char const*>(read(length)), length);
|
|
} else {
|
|
text = "";
|
|
}
|
|
}
|
|
|
|
}
|