About Jesse Liberty
Jesse Liberty has three decades of experience writing and delivering software projects and is the author of 2 dozen books and a couple dozen online courses.
His latest book, Building APIs with .NET will be released early in 2025.
Liberty is a Senior SW Engineer for CNH and he was a Senior Technical Evangelist for Microsoft, a Distinguished Software Engineer for AT&T, a VP for Information Services for Citibank and a Software Architect for PBS. He is a Microsoft MVP.
P.s I was so passionate about that last comment, I typed it all up from my wp7, lol
Impressed with the series so far but one thought did come to mind in this episode regarding the data model you are using between client and server.
Instead of two lists, surely it would be better to just manage one serverid and one clientid per record (or associated id if a record is shared by more than one client)
That way the client knows what records to send to the server by those with no server id, and the client can also request from the server those records with no client id (created on server only)
Obviously both client and server (poss just server) would still need some dedupe logic to merge records where a record was created on both client and server prior to synch.
On another note, instead of batching updates to the server from the client, might be better to just have a queue and keep updates singular to keep it single
Rgds
@ddreaper