On Thu, Feb 4, 2010 at 12:41 PM, harryh <[email protected]> wrote: > > - 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. >
Sure... Please update the ticket: https://www.assembla.com/spaces/liftweb/tickets/2-Mapper-objects-deserialized-from-json-have-all-of-their-fields-marked-dirty- > > ? > > -- > 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]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- 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.
