Archived
This forum has been archived. Please start a new discussion on GitHub.
Protobuf vs. Ice serialization
Hi,
Although I implemented a system using protobuf and ICE sometime ago, I wasn't aware of your support of protobuf until recently. When I viewed the Ice protobuf demo I noticed that you are using Ice serialization mechanism to serialize a protobuf-based object. I'm wondering why you didn't use the protobuf provided serialization and instead sent the data as a string or an array of bytes.
In my application I use protobuf serialization. Using the protobuf serialization seemed to produce more compact messages. Moreover, if you are constantly adding new protobuf messages in your app, you won't need to heavily modify your SLICE interface.
Is there a particular reason why you used Ice serialization instead.
Regards,
Michael
Although I implemented a system using protobuf and ICE sometime ago, I wasn't aware of your support of protobuf until recently. When I viewed the Ice protobuf demo I noticed that you are using Ice serialization mechanism to serialize a protobuf-based object. I'm wondering why you didn't use the protobuf provided serialization and instead sent the data as a string or an array of bytes.
In my application I use protobuf serialization. Using the protobuf serialization seemed to produce more compact messages. Moreover, if you are constantly adding new protobuf messages in your app, you won't need to heavily modify your SLICE interface.
Is there a particular reason why you used Ice serialization instead.
Regards,
Michael
0
Comments
-
Hi Benoit,
I apologize for the hasty inquiry, I didn't examine the code closely. This is exactly how I handle serialization in my application, thanks for the clarification.
Regards,
Michael0
