Internet and Web

The standard and most flexible way to pass custom data to an event handler is to create a custom Event class with public properties to hold the data. The base Event object does not have built-in properties like 'data' or 'payload' for arbitrary data. By extending Event and adding your own properties, you can type-safely pass any data needed by the handler.

MIME stands for Multipurpose Internet Mail Extensions, which extends email to support non-text content like images and audio. Option D is correct with 'Internet' and 'Mail'. Options A and B incorrectly use 'Message' instead of 'Mail'. Options B and C incorrectly use 'Intranet' instead of 'Internet'.

URL stands for Uniform Resource Locator, which is the address of a specific resource on the internet. It tells your browser exactly where to find a webpage, file, or other online resource. The 'Uniform' part means the format follows consistent standards worldwide.

JSP provides four scope options for storing and sharing data: page (default, most limited), request, session, and application (broadest). Page scope only lasts for the current page, request scope lasts for one HTTP request, session scope persists across multiple requests from the same user, and application scope is shared across all users and sessions.

POST is more secure than GET because POST data is sent in the HTTP request body, not visible in the URL. GET appends form data to the URL, making it visible in browser history and server logs, and has length limitations (typically 2048 characters). POST can send much larger data and is the standard method for sensitive information like passwords. Option A incorrectly reverses the length limitations, and Option C is false.

The HttpServletResponse interface provides the getWriter() method, which returns a PrintWriter object for sending character text data to the client. This is the standard way to write response content in servlets. HttpServletRequest (request) handles incoming data, HttpSession manages user sessions, and PrintWriter itself is the class returned, not the source of it. The leading period appears to be a typo but doesn't affect the question.

getAttribute() retrieves object-level attributes stored in the request scope. This is different from getParameter() which retrieves string form parameters from the query string or POST body, and getInitParameter() which retrieves servlet initialization parameters from web.xml. Attributes are typically set by the application using setAttribute() to share data between components, while parameters come from client requests.

At the time of this question's context, approximately 57% of applications in the Android Market were free. This high percentage of free apps was a distinguishing feature of Android compared to iOS App Store, reflecting Android's strategy of rapid app adoption through free applications supported by ads or in-app purchases.

Links do contain Search Specification property (for filtering child records), making option B true. Pick Lists DO have Sort Specification property to control their display order, so option C is false - it's the wrong statement being sought.

The send() method actually transmits the HTTP request to the server (with optional data payload). Option A describes open() which initializes the request. Option B describes getResponseHeader() which retrieves header values. Option C describes abort() which cancels the request. Since none of A-B-C correctly describe send(), D is the correct choice.

The setRequestHeader() method sets a custom HTTP header (name-value pair) that will be sent with the request. It must be called AFTER open() but BEFORE send(). Option A describes send(), Option B describes getAllResponseHeaders(), and Option D describes open().

The responseText property contains the response body from the server as a string. The responseBody property (option A) is not a standard JavaScript XMLHttpRequest property. readyState (option B) indicates the request state (0-4). statusText (option C) contains the status message (e.g., 'OK').

Shared views are designed to be accessible to multiple users in a system. Unlike personal views that are restricted to a single user's use, shared views can be accessed and utilized by many users simultaneously. This makes them useful for collaborative environments where multiple people need the same data perspective.

The first ARPANET message was 'LO' - sent in 1969 by Charley Kline attempting to type 'LOGIN', but the system crashed after the first two letters. This became famous as the humble beginning of networked communication.

The directive <%@ OutputCache Duration="60" %> caches a single version of the page. Without specifying properties like VaryByCustom or VaryByHeader (e.g., User-Agent), mobile devices can receive the cached desktop version of the page. Thus, the statement is false.