>> serialized data is wrapped in an object called a Memento. Then the >> object can be restored using the SetMemento method. So undo can be >> achieved without the host knowing anything about the data, which is opaque. >> It would work, but it requires the params to be opaque if there are >> any of these special cases that we are discussing. When I suggested tha >t >> earlier, people were not happy. > >Ahh, right. Well, if parameters are not opaque, then there's no need to >serialize the entire state, is there? my favorite implementation of the Memento pattern doesn't involve passing data to and fro. instead, the Memento is actually a closure that can be invoked by the plugin. whether or not it contains any actual parameter data or merely a pointer to some private state held by the plugin is an invisible detail. how would such a scheme require that parameters be opaque? --p ---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission. Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe