So, one of the biggest applications I have of UBF type stuff is sending
user profile data between servers. This data tends to be clumped into
batches of tens to thousands of records, consisting of from 1 to a
couple hundred fields. It can also consist of one record for "real
time" data synchronization.
I've tended to send records with name,value pairs, so that empty fields
are not sent. This saves quite a bit of bandwidth of there are just a
few fields to send out of a couple hundred.
My challenge is to apply this to UBF.
First thought, a list of structs of two elements each:
(And yes, I do realize that by taking the field names out of the realm
of UBF(B) that I'm giving up type checking and verification at the
UBF(B) level -- I guess it becomes the application's responsibility --
but it might be nice to explore that some more...)