I have question and 2 answer for this question below that, give comment about th
ID: 3884731 • Letter: I
Question
I have question and 2 answer for this question below that, give comment about these two answer and Feel free to agree or disagree with it (in 2 or 3 short paragaraph)
and for each answer write seprated comment (NOT TOGHETHER)
Be detailed in your postings. Please ensure that your postings are civil and constructive
Question:
Which JSP directive do you prefer (compile time or run time) and why? Discuss.
Answer1:
The decision to opt between a compile time directive versus a run time directive depends on the nature of the application in discussion.
A compile time directive is most likely the option of choice when the goal is to implement an application for which the code being compiled is unlikely to be changed often. This is the case because, since the code doesn’t change often, it won’t be needed to re-compiled the coded for every request the server receives related to it. This maneuver saves time during run time allowing the server to be quicker in responding to a client request.
On the other hand, a run time directive is most likely to be the option of choice when the goal is to implement an application for which the code being compiled is likely to be changed often. This is the case because, since the code changes often, it is preferable to recompile at run time assuring that the latest version of the code is being used to fulfill the request.
Answer2:
I prefer the compile time directive for most cases as there is a higher risk of a run-time exception when using the run-time directive. In addition, the run-time directive adds more overhead as the servlet will make a run-time call to get the included file each time the page is requested. Obviously, it boils down to requirements. In general, if the included files won't be changing then the compile time directive is more efficient.
Explanation / Answer
I prefer Answer 1 because in order to take the decision to opt between a compile time directive versus a run time directive depends on the nature of the application in discussion.
That means the efficiency of application is totally on opting decision.
A compile time directive is most likely the option of choice when the goal is to implement an application for which the code being compiled is unlikely to be changed often.
The program need not satisfy any invariants and it neednot be a well-formed program at all. You could feed this HTML to compile
What things are might be wrong at compile time they are like typo errors,syntax errors and crashes of the complier.
If the compiler succeeds the program will be well prepared.
So then there will be a possible to start running the program.
The inputs and outputs will also being compiled plus any header files, interfaces, libraries, or other voodoo that it needed to import in order to get compiled.
We can also make tht Output hopeful and assembly code, relocatable object code or executable program are goes wrong, output will be in error form.