Re: serialisation in gephex-0.5

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I propose the following solution to this recursive serialisation unit 
> problem:
>
>  * (de)serialisation modules must only have one input and one output 
> port
>    (osc + the type to (de)serialise)
>
>  * additional parameters (quality, etc) can be set by a mechanism 
> similar to that
>    proposed by martin for generic link types (lists, arrays, etc)
>   Think of it like int template parameters in C++
>
> An open issue is the serialisation of osc links themselves...

After some more thinking I believe this is a non-issue (after all osc is
our serialisation format).

Regarding a special interface for (de)serialisation.
We talked about letting core provide a default value for 
deserialisation in the
constructor of the deserialisation units. I think this is a bad idea 
because
it complicates everything (the deserialisation units must remember the 
default
value with a feedback, they need extra logic to decide when to use the
default value, ...)

Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)

iD8DBQFCRUYE/rP0cdKF/ToRAmvEAJ0Try139idvigsrFgoWaoUjE90gjwCeJdtk
WiJmSQNnejQ0ZteDRTGmQ8M=
=7V+z
-----END PGP SIGNATURE-----