[Seaside] ESUG SummerTalk - Fuel, binary object serializer
Mariano Martinez Peck
marianopeck at gmail.com
Wed May 25 08:15:59 UTC 2011
On Wed, May 25, 2011 at 9:55 AM, Runar Jordahl <runar.jordahl at gmail.com>wrote:
> Interesting project. There are so many uses for object serializers.
Yes! We are trying to enumerate them for a paper, so if you can help ;)
> Personally I am looking at storing objects in NoSQL databases, and
> serializing them is an option that will work in a lot of cases.
What would you need as an output of the serializer? a ByteArray ?
> a serializer for copying objects is also useful.
Yep, I think it was Colin who told us he was using his serializer as a
> Does Fuel support “cutting off” instance variables, like SIXX’s
> Object>>sixxIgnorableInstVarNames ?
Not so easily for the moment, but definitely something we will do in the
In fact, we have already an issue for that:
We call them "transient" instance variables. And we want to to extend them
to classes also (so their instances should be ignored as well)
> I always thought SIXX
> (http://www.mars.dti.ne.jp/~umejava/smalltalk/sixx/index.html ) was
> state-of-the-art in this field.
> It seems to have many features, and it
> is supported on many dialects. Are your ideas so great that it really
> makes sense to create yet another serializer?
It is not mostly our ideas, we based our work on VisualWorks Parcels. Of
course, we changed several things but the idea of the pickling format is
> Wouldn’t improving SIXX
> be better?
Because we DON'T want to use text based serializers. It is impossible to get
real speed with a text based serializer. We want to be really fast, that's
our main goal.
Try to use SIXX to export a Moose model for example. I recommend you to take
So....purposes and goals are different. Our mail goal is speed, and mostly,
materializing speed. That's why we are using a particular pickle format.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside