Hey all, Can someone help me understand the synchronization and dirty-marking requirements surrounding Session#setMetaData()? I thought the rules for Session use were (1) synchronize data access, (2) call Session#dirty() after data changes to replicate the changes across the cluster. However, I don't see either of these happening in Wicket's internal use of Session MetaData. Is this an oversight, or am I missing something?
Thanks, Dan
