I've got some questions after using this library

[ysmoradi]

Hello,

After using the CommunityToolkit.DataSync library for some time, I have a few questions/observations:

1. The library does not use $batch to send all changes at once (instead of sending many separate requests), which is fine — I know implementing $batch is not easy.
   But when there is no benefit from $batch, why inherit from ODataController instead of ControllerBase? All OData features except $count and $batch work perfectly well with regular API controllers too.
   CommunityToolkit.Datasync.Server.Swashbuckle, CommunityToolkit.Datasync.Server.NSwag, CommunityToolkit.Datasync.Server.OpenApi seems to be added for the same reason.

2. Is there a specific reason for having both Version (byte[]) and UpdatedAt properties?
   These appear somewhat redundant, as UpdatedAt is presumably updated every time a record is modified. In many scenarios, a timestamp alone can be used for optimistic concurrency control. Using UpdatedAt as the concurrency token would eliminate the need for a separate Version property. Am I overlooking a particular use case or requirement that justifies keeping both?

Thank you for the great toolkit and for any clarification you can provide!

[adrianhall]

1. I haven't got around to implementing it yet. It's on my todo list (but, as you will read elsewhere, I'm moving to Europe right now). Agreed on ODataController vs. ControllerBase - that's legacy, to be honest. I found certain (non-obvious in-the-depths) OData functionality doesn't work with ControllerBase (most notably, the hook for geo-lookups).
2. Yes, there is - Version is for the very specific task of passing the optimistic concurrency tokens from the DB to the client in a round-trip compatible way. UpdatedAt is for doing incremental sync. I had thought about using UpdatedAt ONLY, which encapsulates both. However, certain databases don't guarantee uniqueness of the value, so I'm at a stop there.
3. You also mentioned the OpenAPI processors - these are specifically for supporting the individual OpenAPI generators. I've figured out a new way to do this (which is good!) but I can't do it yet because it required dotnet 10 (in all cases). However, I have it on my mind. These should all go away in a future release.

[ysmoradi]

Really appreciate efforts on this project 💯