Asynchronous CRUD operations?

edwinsn · 2014-05-19 15:25:24

Hi Arnaud,

Can the object CRUD operation be asynchronous?

My application is a standalone program, some threads will download something from the Internet and let the ORM server (using the named pipes protocol) to save the data.

And I don't want those 'downloader threads' to wait for the ORM server to finish saving data, but just post the job to the ORM and forget.

ab · 2014-05-19 18:24:01

There is no such function yet.

You have to create your own thread for any asynchronous process.
You can use a library for that - like http://otl.17slon.com/

edwinsn · 2014-05-20 03:26:21

@ab,

I think I just got my answer by a reply of yours in another topic, by setting the following:

TSQLRestServerDB.AcquireExecutionMode[execORMWrite] := amBackgroundThread

And all the writing to the sqlite3 db will be run in another single, dedicated background, thread, right?

Last edited by edwinsn (2014-05-20 03:50:56)

edwinsn · 2014-05-20 03:53:36

Oops, looks I myself is a little confused with my own question - with TSQLRestServerDB.AcquireExecutionMode[execORMWrite] := amBackgroundThread, the client still have to wait for the result of that background thread...

I already know the OTL threading library, but I want to make my program ready for inter-machine/process client/server architecture. I still need some thoughts...

edwinsn · 2014-05-20 06:25:35

Well, looks I can use threads on the client side too...

ab · 2014-05-20 06:33:01

On the client side, there is some background process built-in.
See http://blog.synopse.info/post/2013/07/0 … responsive

edwinsn · 2014-05-20 10:25:16

thanks for the info, that approach is not suitable for my case, I'll use threads on the client side.

ab · 2014-05-20 10:38:48

Be aware that, in your case, I suppose each client thread should have its own TSQLRestClientURI instance, otherwise any shared instance will be blocking, so you will not benefit of multi-threading.

edwinsn · 2014-05-20 12:13:05

ab wrote:

Be aware that, in your case, I suppose each client thread should have its own TSQLRestClientURI instance, otherwise any shared instance will be blocking, so you will not benefit of multi-threading.

Sure, and thanks!

mORMot Open Source

#1 2014-05-19 15:25:24

Asynchronous CRUD operations?

#2 2014-05-19 18:24:01

Re: Asynchronous CRUD operations?

#3 2014-05-20 03:26:21

Re: Asynchronous CRUD operations?

#4 2014-05-20 03:53:36

Re: Asynchronous CRUD operations?

#5 2014-05-20 06:25:35

Re: Asynchronous CRUD operations?

#6 2014-05-20 06:33:01

Re: Asynchronous CRUD operations?

#7 2014-05-20 10:25:16

Re: Asynchronous CRUD operations?

#8 2014-05-20 10:38:48

Re: Asynchronous CRUD operations?

#9 2014-05-20 12:13:05

Re: Asynchronous CRUD operations?

Board footer