Hello,

I'm using a TFPHTTPServerHandler in threaded mode. I'm also using a TJSONRpcModule.
I see that, even if the calls come from different threads, only one instance of the rpc module is ever created (on demand, the first time an rpc request comes in) and used.
Since I'm relying on this behaviour, can I be 100% sure it's by design and not a quirk of my test setup?

Bye

It is controllable.

There is the 'Modulekind' : wkPooled.

Type
   TWebModuleKind = (wkPooled, wkOneShot{, wkSession});

And a property of your module:

  property Kind: TWebModuleKind read FWebModuleKind write FWebModuleKind default wkPooled;

wkPooled is the default, but if you explicitly set this to 'wkPooled' in the constructor, you'll be sure there is only ever 1 instance of the module, which is reused for every request...

Michael.

El 21/10/22 a les 9:39, Michael Van Canneyt via fpc-pascal ha escrit:

Thank you,

I see that the property isn't published, so it's not available in the object inspector.
Can I set it in the DataModuleCreate os is it too late?

Bye

El 21/10/22 a les 9:48, Luca Olivetti via fpc-pascal ha escrit:

I overrode the CreateNew method, I hope that's enough.

Bye

El 21/10/22 a les 9:57, Luca Olivetti via fpc-pascal ha escrit:

I see that Kind is used after the module has been created, so setting it in either method (CreateNew or DataModuleCreate) should be OK, am I right?

Bye

You are right.

I will publish the method. That's an oversight.

Michael.

El 21/10/22 a les 12:48, Michael Van Canneyt via fpc-pascal ha escrit:

Meanwhile I changed the method I use to route the calls to the main thread (Application.QueueAsyncCall instead of a critical section and Synchronize) so it doesn't matter any more if there is just one instance or more than one.

Bye

El 21/10/22 a les 17:09, Luca Olivetti via fpc-pascal ha escrit:

Now that I think of it, even with the previous method it wouldn't have mattered (since each instance would have been using its own critical section and other fields).

Bye