Communicating with a Server - Summary

In this article, I demonstrated how to load the contents of a URL and convert that content into something that can be displayed within a mobile application. In addition, I demonstrated that it's not difficult to ensure that this feature is implemented in a thread other than the main UI thread.

For an example this small, it may not be possible to see the sluggishness. However, as I've said before, things that start off small tend to end up getting large, so it's best to practice good design from the beginning.

I also mentioned concerns with an unstable business object model. If I'm rapidly iterating on changes to the model, then it's quite possibly an indicator that I haven't spent enough time thinking about the problem I want to solve. For me personally, I keep a spiral notebook handy, and write my thoughts down as they come to me. I usually have a few of these brainstorming sessions before I return to the keyboard to write code. And although this practice isn't that unique, it helps me ensure that I've carefully considered the problem I want to solve.

At this point, I've simply read data and displayed it on the map. You may recall, however, that I implemented create, edit, and delete methods on the server. I haven't implemented their counterparts yet, because I first need to secure the communication between the client and the server. That will be the topic of the next article: Secure communication.