Moving Code to Other Threads
Registered by
Nathan Osman
on 2011-04-03
Some of the code in StackApplet ties up the GUI and some of the new HTTP stuff will make this even worse. Therefore a need exists to move a lot of the code to a new thread.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Nathan Osman
- Definition:
- Approved
- Series goal:
- Accepted for 1.5.0
- Implementation:
-
Beta Available
- Milestone target:
- None
- Started by
- Nathan Osman
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
In the 1.4 series, everything is in one thread... which is inefficient and bad practice.
Current status:
- Thread 1 is responsible for initialization and the GUI
- Thread 2 is responsible for network requests to and responses received from the SE API
- Thread 3 is responsible for the HTTP server used by the preferences pages
Each of these threads is separated and properly synchronized.
(?)
