mORMot

Yes, use ALL_FIELDS or your custom field bits for the `Add` and `Update` methods

Eugene Ilyin wrote:Please let me know if the issue is gone or still exist on the latest mORMot revision when you add this line to the end of your source code. Eugene with your modification the issue is gone, thanks a lot! Thanks also macfly for your kind suggestion.

I don't use this feature on Windows, but I use Daemon on Linux.I had problems, for obvious reasons, when using relative paths in the code (settings files), por example path of db.The forked application could not find the files, because it was running in another context.

Yes, thanks you all!It is not the first time I have seen some minor differencies in behavior in TThread, in Delphi and FPC.Nice seeing at least one problem seems solved!

@zed, I use SynSQLite3Static.pas

Got it,  thanks.

You are right, it was TAESCFB on mORMot 1.18, but we switched to TAESOFB with mORMot 2, which is faster on x86_64 in our unit, and slightly more proven.SHA-3 can be used in XOF mode, generating an endless output stream (not limited to 128, 256 or 512 ... [More] bits).We have a TSha3.Cipher() method which uses it as a cryptographic secure hasher. Slower than AES-NI (aes128ofb is 750MB/s, Shake128 is 160MB/s on my PC), but very safe and proven.For instance, we use it in TAesPrng.GetEntropy to enhance the operating system-derivated entropy.It is good to mix proven algorithms when you want to increase security.Accept-Encoding is not a good idea, since it is not mandatory in the HTTP standard. You can still send data with no encoding, and it would be valid.TLS is a much better option (we usually use a nginx reverse proxy + Let'sEncrypt for it), or encrypting the WebSockets binary frames as we do. [Less]

Ok found the problem, @mpv you were right, the clones are destroyed without waiting for thread to terminate gracefully,solution :procedure THttpApiServer.DestroyMainThread; ... for i := 0 to length(fClones)-1 do begin fClones[i].WaitFor; //<--- fClones[i].Free; end;

I will do & see.Yessss, it works without modification of the Get Procedure.

yes that should work (for that specific example), Err event could be called several times so you should make sure the postmessage is sent only once when needed.