Guide to structure structure / life cycle?

Question

Is there any reason to switch from the default area (transitional?) To something else, beyond the need to control the area for functional reasons (for example, Singleton)?

If I stick to the default scope, each default instance of each type of plugin will be effectively created on every request (assuming the web application), is this correct? Could this affect performance noticeably?

I considered using the Http Session scope to limit this to one instance for each registered user. However, this will result in (at least) one instance of each type of plugin stored in memory for each user at any time. Using the default scope, these instances will only be stored in memory during the processing of the page request. I am not sure which is preferable.

If you use StructureMap, how do you usually customize the scope for each of your plugin types?

Thank you for understanding,

Phil

Answer 1

I leave the default area in place. This means that for each request (either by each user or by many users) I have an instance of the object in my hand. This means that a new request is created each time. Keeping it in the session is what I prefer to have more specific control. For this reason, I can drop the cache layer on top of the service level and insert a StructureMap object into it. Then I can request a cache for an already created (now serialized) object and choose where to get my objects from.

I would do the same for the Singleton configuration, where I would use StructureMap to get the actual object ... but when it returns to the object for the second time, the object itself will transfer the instance to itself (in Singleton). It uses StructureMap to power it ... but it does not give it more energy than necessary.