Index: src/core/SkFlattenableSerialization.cpp |
diff --git a/src/core/SkFlattenableSerialization.cpp b/src/core/SkFlattenableSerialization.cpp |
index b74c82f051648f77dce5da97b26e21ba53b12e4b..7b7a61679479394d1dbc36b2af523cf7adefb3a8 100644 |
--- a/src/core/SkFlattenableSerialization.cpp |
+++ b/src/core/SkFlattenableSerialization.cpp |
@@ -9,12 +9,12 @@ |
#include "SkData.h" |
#include "SkFlattenable.h" |
-#include "SkOrderedReadBuffer.h" |
+#include "SkSecureReadBuffer.h" |
#include "SkOrderedWriteBuffer.h" |
SkData* SkSerializeFlattenable(SkFlattenable* flattenable) { |
SkOrderedWriteBuffer writer(1024); |
- writer.setFlags(SkOrderedWriteBuffer::kCrossProcess_Flag); |
+ writer.setFlags(SkFlattenableWriteBuffer::kSecure_Flag); |
reed1
2013/08/29 19:08:22
Why does Serialize now imply Secure?
sugoi1
2013/08/29 19:39:40
To be symmetrical with the secure read operation,
|
writer.writeFlattenable(flattenable); |
uint32_t size = writer.bytesWritten(); |
void* data = sk_malloc_throw(size); |
@@ -23,6 +23,6 @@ SkData* SkSerializeFlattenable(SkFlattenable* flattenable) { |
} |
SkFlattenable* SkDeserializeFlattenable(const void* data, size_t size) { |
- SkOrderedReadBuffer buffer(data, size); |
- return buffer.readFlattenable(); |
+ SkSecureReadBuffer reader(data, size); |
+ return reader.readFlattenable(); |
} |