Could you clarify the lifetime and ownership of
TServerRequestQueue.GetNewRequest returns please? If I call it, who
owns the allocated request? When does it get freed? Is that something
that happens automatically after the callback, or some other time?

--

Matthew Jones

On 6/29/2016 11:38 AM, Matthew Jones wrote:
> Could you clarify the lifetime and ownership of
> TServerRequestQueue.GetNewRequest returns please? If I call it, who
> owns the allocated request? When does it get freed? Is that something
> that happens automatically after the callback, or some other time?
>

We have the framework source and my interpretation after looking at it
is as follows:

- the main benefit of using GetNewRequest (over just doing
TServerRequest.Create in your code) is that TServerRequestQueue
maintains a pool of requests and can return one of those

- at that point you own it

- however if you add the request back to the TServerRequestQueue  then
it will own it for you (and once complete or cancelled will add it to
the available request queue again)

Raul

Raul wrote:

> We have the framework source and my interpretation after looking at
> it is as follows:
>
> - the main benefit of using GetNewRequest (over just doing
> TServerRequest.Create in your code) is that TServerRequestQueue
> maintains a pool of requests and can return one of those
>
> - at that point you own it
>
> - however if you add the request back to the TServerRequestQueue
> then it will own it for you (and once complete or cancelled will add
> it to the available request queue again)

Okay, that's handy to know. Would be good to have that documented in
the help so one can know to "not care" too much.

--

Matthew Jones