>> Not necessarily - it may return only constant-type objects to the user. One >> idea is that it would just return the address of the node wrapped in an >> object that clarifies the intent. So in that case there is no more memory >> required in the underlying mesh than currently required. > > This is nice memory wise (and unlike Derek, I do shudder at the idea > of adding more bytes-per-node), but then there's no way to safely pass > nodes from one processor to another without losing that > identification. Static ids are much preferable to that.
Oh absolutely - more state would need to be handled when shipping objects around. I'm not too worried about that though - I'll try to think of a fix for that. -Ben ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
