I'm curious if anyone here has used protobuf to serialize DataSets? I
saw an earlier discussion, but it didn't seem to go anywhere.
If DataSets are not currently serializable, how would I go about
making them serializable? My main goal here is performance and space,
not necessarily
If you mean . Net data sets, I blogged about this earlier this week:
marcgravell.blogspot.com
Note I only experimented with a single DataTable, but that is most of the
hurdle. The code using protobuf-net v2 is **experimental** and incomplete, but
committed. If if is something you'd be
Yes, I do mean .Net DataSets, and I am interested in this. Your blog
post is very awesomely cool to me! We will be at a point in a couple
of weeks were I will want to evaluate this for some alpha development
we are doing. If it isn't yet able to serialize a full DataSet, I can
certainly try to
Note that I only includes enough code to handle the specific example in the
blog experiment.
For the sake of the group, this discussion centres around an implicit contract
inferred from a table structure, but persisted as a valid protobuf stream (a
.proto could also be generated in theory).
On Oct 14, 2:30 pm, Evan Jones ev...@mit.edu wrote:
On Oct 14, 2010, at 11:32 , CB wrote:
Actually, yes, we have a shared library containing our protobuf code,
which we do load with dlopen. A command line option tells the app
which protocol it needs to use, and the app loads the
