Opened 12 years ago
Last modified 9 years ago
#4 new enhancement
Chain requests
Reported by: | sander | Owned by: | sander |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Central server | Keywords: | |
Cc: | Time estimate: | 12 hours (simple version) |
Description (last modified by sander)
Users want to change requests instead of running them parallel. For example, an uploaded document is rountripped through OpenOffice.org, KOffice, AbiWord?, etcetera in sequence. They want access to the intermediate results as well as the end result.
This may be too complicated to integrate in the server directly. The same effect can be achieved with a separate application using a user API. See #3.
Change History (5)
comment:1 Changed 12 years ago by sander
- Description modified (diff)
comment:2 Changed 12 years ago by sander
comment:3 Changed 12 years ago by sander
- Time estimate set to 8 hours (simple version)
comment:4 Changed 11 years ago by sander
- Time estimate changed from 8 hours (simple version) to 12 hours (simple version)
comment:5 Changed 9 years ago by iwdy23
cartier replica not easy
Note: See
TracTickets for help on using
tickets.
A simpler version of the "Chain Request" feature would be a button on the result page to re-submit the result document as a new request.