on 07-17-2012 8:24 AM
Would hook method WDDOEXIT of the component controller be called if somewhere in the component a piece of code, or some unforeseen situation, causes a short dump?
Our scenario is fairly simple:
Now, while working on the work item, a short dump occurs, the work item stays reserved and the other user cannot work upon it, as the Hook methods mentioned in step 3 are not being called.
How to ensure that even in case of abrupt or disgraceful termination of application, the work item is workable for other users?
As per my understanding, WDDOEXIT would not be called on dump.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That was pretty straight, even if trite. I understand your point, but there can be situations which are out of a programmer's control. For instance, time out on account of connectivity or too long a selection, unavoidable due to business requirements or simply, unusual traffic on a particular day. So, even if one handles all perceived situations and known exceptions, there can be unforeseen situations - as I mentioned in the original post - that can cause dumps.
The idea is to have a robust code. Something which is synonymous with your definition of 'good application'.
Any more ideas?
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.