> - Serializing the dirty-state of each field (e.g., field_name_$dirty:
> true)

This further increases the size of the serialized objects which is not
ideal

>  - A thread-local flag for the default dirty/clean
>   - A global flag indicating that the fields are marked clean/dirty on
>   deserialization

And these seem no good due to the user of global variables

What about option 4:

- change the deserialize function to take an extra parameter
indicating whether the fields should be marked dirty or not.

?

-- 
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.

Reply via email to