| Summary: | [api] allow SubmitTaskJob to not fetch TaskData afterwards | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Thomas Ehrnhoefer <thomas.ehrnhoefer> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | shawn.minto, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 353458 | ||
|
Description
Thomas Ehrnhoefer
We could consider adding a flag to suppress fetching of task data. To clarify, are you looking for a way to modify the synchronization behavior of the tasks framework or for an API in SubmitTaskJob, e.g. when directly invoking the job? synchronization behaviour of the tasks framework. The main issue at hand in my current example is that during submitting a new task (which is a two step process, one creating the server task, one updating it with the taskdata) fires two events from the server, the first one usually coming in before the the submitTaskJob is done. That triggers fetching of taskData too early and causes an incoming notification. Delaying the event processing of "new task" fixes this, but it seems to be a general problem for servers with a push model. So this is not urgent for me, but should get addressed when addressing the support for push model I think. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |