ClassInstVar changes aren't flushed or faulted
ClassInstVarConnectors do connect properly on the first login, but changes
aren't propagated because of issues with marking a class as dirty.
Workaround
A workaround would be to use a value model like an Association instance
in the classInstVar to hold the value that would normally be put in the
classInstVar. Code would then access with #value and #value: in both the
client and server code to ensure changes are propagated as the association
is dirtied.
Last updated: 7/18/11