next up previous contents
Next: Error Pages Up: MIC Error Handling Previous: Conditional Verification   Contents


Page Verification

Though usually less preferred than vinstantiated, there might be times in which a user wishes to use vpage. Such an instance might be if the verification for fields is particularly costly for some reason, and/or a great number of fields are being instantiated, many of which we do not wish or need to re-verify.

If vpage is used, one must be very cautious about state errors. Realize that all the code within a page will be run again in order to determine what is on the page. The page is essentially redisplayed at time of verification, although there is no output to the user. This means that for vpage to function without any unexpected side effects, the page must be more or less side effect free, at least when it is called again to be verified.

Though considered bad style, it may be necessary to case out when the page is being called. That is, put the sections of the page that will cause `bad' things to happen if they are run twice in if-statements and have some sort of global flag5.1 or HTML parameter that signals that the block in question should not be run.


next up previous contents
Next: Error Pages Up: MIC Error Handling Previous: Conditional Verification   Contents