Hi all,
question regarding the cleanup of dynamic objects and the use of a widget pool. Speaking in regards to a webspeed application. I noticed we have some dynamic queries where we are not deleting the handle object.
I want to make sure I do proper deletion of those objects. My question is regarding the use of a widget pool. In a web environment obviously things can time out for various reasons. From reading this article it makes an interesting point about the advantage of using a widget pool if an app errors out. Even if you delete a handle, if the app errors out the memory leak can still occur. using a widget pool can keep this from happening if the app errors out.
Speaking in regards to a web app via webspeed is it good practice to "always" create a widget pool to store the handle? Are their times you dont want to do this?
If I have a search page that gets a lot of requests is it bad to do a constant create and delete of a widget pool for each and every request?
question regarding the cleanup of dynamic objects and the use of a widget pool. Speaking in regards to a webspeed application. I noticed we have some dynamic queries where we are not deleting the handle object.
I want to make sure I do proper deletion of those objects. My question is regarding the use of a widget pool. In a web environment obviously things can time out for various reasons. From reading this article it makes an interesting point about the advantage of using a widget pool if an app errors out. Even if you delete a handle, if the app errors out the memory leak can still occur. using a widget pool can keep this from happening if the app errors out.
Speaking in regards to a web app via webspeed is it good practice to "always" create a widget pool to store the handle? Are their times you dont want to do this?
If I have a search page that gets a lot of requests is it bad to do a constant create and delete of a widget pool for each and every request?