From before we have had the PersistenceMapperWCFClient that connects to a RemotePeristenceMapper (like the MDrivenServer is one example of).

We now also have the PersistenceMapperWEBAPIClient - it does the exact same thing but does not use WCF - instead it defaults to transport over https.

The main reason for this novelty is that Microsoft is moving away from WCF in .netStandard and ASP.Core.

As we introduced the PersistenceMapperWEBAPIClient we also added a few new functions that we have found useful:

The ability to compare checksum between client and server of the model content. This is important since a client that has the wrong model cannot be allowed to save objects to the server. Since we want to notify the user of this as soon as possible we need a way to find this fact out very early in the client-application -lifecycle.

Another useful function is the "Closed for business" message. This is useful in environments that require some downtime in order for maintenance - like a new deploy.

Checksum