[Dune] Communicating IdSet elements
Jö Fahlke
jorrit at jorrit.de
Sun Jul 24 16:52:38 CEST 2011
Am Sun, 24. Jul 2011, 16:31:27 +0200 schrieb Martin Nolte:
> Either way, I think we need to add two important properties a global id has to
> satisfy:
> 1) there must be an easy way to communicate it
As long as you're using a CollectiveCommunication, this currently works by
communicating the bit pattern as far as I know. While this works in practise,
there is no guarantee that it will work for any type of id someone could
possibly think of, and of course it is hackish.
> 2) it needs to support (disk) I/O
I think we need to be more precise here: writing the id to a text file is as
easy as providing operator<<() (and operator>>() for reading).
When you think of stuff like checkpointing however, you probably want to have
a way to store the Id in a binary representation to save space and thus speed
up writing. This calls more for a general serialization framework, and indeed
that would also help to achieve safe communication.
Bye,
Jö.
--
F: Was ist der Sinn des Menschen?
A: Die Menschheit voranzubringen.
F: Aber was ist der Sinn der Menschheit?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20110724/ffb994eb/attachment.sig>
More information about the Dune
mailing list