Building MIDlets - Beginning J2ME: From Novice to Professional - page 22

In the first edition of this topic, Jargoneer connected directly to the Jargon File server. In
response to its query, it received a lot of information it didn't need. The original Jargoneer went
to considerable trouble to parse through the HTML response to extract the definition it wanted.
Architecturally, the old Jargoneer looked like Figure 2-4.
Figure 2-4. Jargoneer architecture
The new architecture is shown in Figure 2-5.
Figure 2-5. A cleaner architecture for Jargoneer
Instead of hitting the web server directly, Jargoneer goes through a different server hosted
by Apress. This server queries the Jargon File, parses the result, and returns the definition to the
device. This is advantageous from several standpoints: