Rest API Stateful
Posted: Sun Feb 21, 2021 4:16 pm
I've been having a look at how state is handled in the REST api and from what I can see it is handled by the ObjectDictionary on the manger, which seems simple enough, my question is this what happens if stateful requests aren't abandoned, my reason for asking is I need to create a two route process one where a list of information will be retrieved and another where that same list will be posted back to the api and then changes will happen based upon how the items are changed in the second request.
Whilst I could create the list a second time I would prefer not to as this will be reasonably database intensive and plucking it out of the ObjectDictionary would be easier but my question is what about if the second call never happens are things going to chew up memory or is the ObjectDictionary cleaned up when a sessions ends i.e. the manager is logged off and the ObjectDictionary cleared?
By the way when using an api key should you still explicitly call logout regardless of using state?
Whilst I could create the list a second time I would prefer not to as this will be reasonably database intensive and plucking it out of the ObjectDictionary would be easier but my question is what about if the second call never happens are things going to chew up memory or is the ObjectDictionary cleaned up when a sessions ends i.e. the manager is logged off and the ObjectDictionary cleared?
By the way when using an api key should you still explicitly call logout regardless of using state?