I have quite a complex capability, with some collections. I thought that it would be too troublesome to create network messages for every operation I make, so I instead used the storage class to serialize the whole capability class and send it to the client. I then added some methods on the capability class to replace the references in the fields with the ones from the deserialized class. The performance loss is insignificant, as I will rarely be using it.

Is there anything I should be concerned about? 

You should only send the data which has changed.
You could create a message that uses a Collection as parameter,
if you then change the data of a collection, you can send this message with the new Collection to the client

Note: you also need a parameter that defies which Collection is to be synchronized on the Client (a String or an int are recommended)

Edited November 20, 20213 yr by Luis_ST

14 minutes ago, Luis_ST said:

You should only send the data which has changed.
You could create a message that uses a Collection as parameter,
if you then change the data of a collection, you can send this message with the new Collection to the client

Note: you also need a parameter that defies which Collection is to be synchronized on the Client (a String or an int are recommended)

By collections, I mean maps of lists and such. Syncing will be a pain. If there is no immediate issue other than a little performance loss, I will just keep it like that until i do a refactoring and cleanup session on the code.

5 minutes ago, matthew123 said:

By collections, I mean maps of lists and such.

then you need to create two messaages, also Lists are an instance of Collection

5 minutes ago, matthew123 said:

If there is no immediate issue other than a little performance loss

if you don't sync the data very often, that shouldn't be a problem