There have been posts to the Nokia forums indicating that there is some
benefit to having thread objects that exist just long enough to make an
HTTP request. In other words, each time I want to make an HTTP request I
spawn a new thread and it lives just long enough to get a response from the
server:

HTTPThread http = new HTTPThread("http://www.foo.com"); http.start();

// ...

public class HTTPThread extends Thread
{
public void run()
{
// Do HTTP request and die
}
}

This seems like it would incur quite a nasty cost in memory
allocation/garbage collection. The alternative is to have a thread that
stays alive:

HTTPThread http = new HTTPThread();
http.start();

// ...

http.Request("http://www.foo.com");

// ...

public class HTTPThread extends Thread
{
private String url;

public void Request(url)
{
this.url = url;
}

public void run()
{
while (true)
{
if (url != null)
{
// Do HTTP request
url = null;
}

yield();
}
}
}

Which strategy is preferred for the Nokia 3650? Are there hidden firmware
gotchas that may prevent the second example from working?