At the moment I'm engaged in carrying out a lot of work to improve response times in our WCF / LLBLGen Adapter based WinForms thin client application (which has service methods such as void SaveCustomer(CustomerEntity customer) etc. ). I'm thinking of switching to using a custom binary serialization implementation for WCF in order to take advantage of the far smaller message sizes but also the fact that UnitOfWork2.OptimizedSerialization = true allows one to serialize just the unitofwork queues that were generated from a big entity graph (with both clean entities and dirty entities).
So as a result:
work.AddForSave(customer, true);
ServiceEndPoint.CommitUnitOfWork(work);
would be far more performant (i.e. the message size is smaller) than doing
ServiceEndPoint.SaveCustomer(customer);
then doing the usual adapter.SaveEntity(customer, true) .
So am I correct in thinking that remoting / any implementation using BinaryFormatter to serialize llblgen entities and UnitofWork2 instances not only gives a smaller message size, but allows one send only the data required for the db inserts and updates over the wire, rather than the entire graph?