Let's assume I'm designing a distributed (client-server) application.
The server owns a bunch of parameters. The client (GUI) is to be
periodically updated when any of their values change.
i) send a small wire message containing one field each time it changes
ii) periodically send a big wire message containing only the fields
which have changed
iii) periodically send a big wire message containing all current
Which approach is best and why?
Should optional fields only be added/removed at design-time, or is it
ok to vary their presence at runtime too?
How do I learn best practices for designing messages and exchange
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at