Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350026 - Improvements in the task framework to consider
Summary: Improvements in the task framework to consider
Status: CLOSED WONTFIX
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Anton McConville CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-22 06:06 EDT by Szymon Brandys CLA
Modified: 2017-01-10 15:39 EST (History)
6 users (show)

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 Szymon Brandys CLA 2011-06-22 06:06:05 EDT 
I think there is a place for improvements in our task framework. If there is a task-based operation and it finishes quick, we could just return the result immediately instead of sending the task location. We could define how long we wait for the result and after this time we could just get the task location and start polling.
Comment 1 Malgorzata Janczarska CLA 2012-03-15 07:43:13 EDT 
I assume that it is me that will be doing this task. If somebody wants to do it let me know.
Comment 2 Malgorzata Janczarska CLA 2014-09-12 08:05:48 EDT 
This one is partially done: all that is left the we should allow to define the timeout by the client (right now it's only set on the server side).
Comment 3 Eric Moffatt CLA 2015-09-29 14:43:40 EDT 
Folks, can we mark this one as done ? I'm thinking that allowing the user to set something as deep as the task response timeout is micro-management (i.e. would users know or care that such an option is available ?). As long as the time makes sense for us...
Comment 4 Eric Moffatt CLA 2015-09-30 10:39:49 EDT 
Oops, I may have misunderstood the last comment. If this is just a way for the client code to define what the timeout is then that's fine since certain pages may benefit from a different timeout.

I was thinking that we'd have a user preference which would be a bad idea IMO.
Comment 5 Michael Rennie CLA 2017-01-10 15:39:47 EST 
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:

https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04002.html