Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345842 - Make Synchronizer and TimerExecSchedule serializable
Summary: Make Synchronizer and TimerExecSchedule serializable
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.5 M1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 342407
  Show dependency tree
 
Reported: 2011-05-15 08:38 EDT by Rüdiger Herrmann CLA
Modified: 2011-07-04 08:57 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-05-15 08:38:02 EDT 
Synchronizer and TimerExecScheduler are responsible to execute Runnables that were passed in to Display#syncExec(), #asyncExec() and #timerExec().
If possible, these runnables (if they implement Serializable themselves) should be serialized and deserialized as part of the serializing the Display.
Comment 1 Rüdiger Herrmann CLA 2011-06-30 10:12:54 EDT 
Runnables posted via (a)syncExec() can now be migrated to another node and be executed there.
Comment 2 Rüdiger Herrmann CLA 2011-07-04 08:57:02 EDT 
Runnables posted via timerExec() can now be migrated to another node and be executed there. Changes are in CVS HEAD.