Threads

[Ghost]

I am trying to determine the best way to manage my Threads. Here is my
situation:

- I have a website that requires a user to login.
- When the user logs in, this creates an instance of my WebUser class.
- WebUser creates a new thread for each new user.
- The WebUser class is used to access information from my server. If
the user requests information from the server (by hitting a web page),
WebUser calls something like: getUserInfo().

Currently, WebUser implements Runnable. When WebUser creates a new
thread, that thread basically performs the following run function:
public void run() {
sleep(1000)
}

WebUser does not need to do anything until the user requests
information. Right now it just sleeps all the time.

Is there a better way to handle the WebUser threads? Should WebUser
subclass Thread?

Thanks for any advice.

 

[Anton Spaans]

I am trying to determine the best way to manage my Threads. Here is my
situation:

- I have a website that requires a user to login.
- When the user logs in, this creates an instance of my WebUser class.
- WebUser creates a new thread for each new user.
- The WebUser class is used to access information from my server. If
the user requests information from the server (by hitting a web page),
WebUser calls something like: getUserInfo().

Currently, WebUser implements Runnable. When WebUser creates a new
thread, that thread basically performs the following run function:
public void run() {
sleep(1000)
}

WebUser does not need to do anything until the user requests
information. Right now it just sleeps all the time.

Is there a better way to handle the WebUser threads? Should WebUser
subclass Thread?

Thanks for any advice.

Why do you want to create a thread? Threads (created or re-used for each
http-request) are managed and handled by the web-server/container. Don't
create and try to manage your own threads, especially if there is not an
absolute requirement for it:

- User logs in.
- The http-request from this log-in goes arrives at your web-server.
- Create a new WebUser instance, cache it, and Call the 'getUserInfo()'
(directly, not via a thread).
- Do some other stuff.
- Write the response (http-response) back to the browser.
- Browser displays the response.

- User goes to next page.
- The http-request goes to your web-server.
- Based on the user, get the correct WebUser from the cache.
- Using the WebUser (config info?), handle the rest of the request.
- etc..

BTW: How do you handle the deletion of WebUser instances (when users go
idle)? You should use the http-session instead.