Which of the following is considered the best way to design a flexible API that does not require a servlet per activity?

Which of the following is considered the best way to design a flexible API that does not require a
servlet per activity?

Which of the following is considered the best way to design a flexible API that does not require a
servlet per activity?

A.
Create a query string containing the activity name as a parameter. Let the servlet read the
parameter to determine what must occur.

B.
Use a servlet mapping to make requests with the same suffix. Change the prefix to the action
and let the servlet read the whole URL to determine what is required.

C.
Embed the activity name in a hidden field. Let the servlet read the field to determine what must
occur.



Leave a Reply 0

Your email address will not be published. Required fields are marked *