Issue 80374 - Add possibility to cancel a loadComponentFromURL() request
Summary: Add possibility to cancel a loadComponentFromURL() request
Status: REOPENED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-06 10:50 UTC by mnasato
Modified: 2013-07-30 02:37 UTC (History)
2 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description mnasato 2007-08-06 10:50:18 UTC
It would be nice to be able to cancel an XComponentLoader.loadComponentFromURL()
request, in the same way that e.g. XFrameLoader has a cancel() method for its
load() one.

Related discussion on the api-dev mailing list

  http://www.mail-archive.com/dev@api.openoffice.org/msg05901.html
Comment 1 andreas.schluens 2007-08-06 11:18:36 UTC
My area .-)
Comment 2 Mathias_Bauer 2008-05-19 09:32:19 UTC
Only the asynchronous frame loader has this method and as loadComponentFromURL
is a synchronous call it shouldn't use asynchronous frame loaders at all. IMHO
asynchronous frame loaders should become deprecated.

Anyway, it doesn't make sense to have a "cancel" in a synchronous method (as it
can't be canceled anymore when it returns).
Comment 3 Mathias_Bauer 2008-05-19 09:33:06 UTC
closing
Comment 4 mnasato 2008-05-19 11:28:19 UTC
The business case for this Feature Request is clear - if you read the related
mailing list discussion that originated it.

Some documents may take a long time to load, and in some scenarios it would be
better to interrupt the loading operation and just return a message to the user
saying "Sorry, your document could not be loaded", rather than making him wait
for several minutes.

If the current implementation of loadComponentFromURL cannot be interrupted
because it's synchronous, then provide an asynchronous one that can be interrupted.

In any case, I don't think that this request can be considered INVALID,
different people have agreed that it would be a useful feature and 2 persons
(not me) have voted for it.

For this reason I am reopening it.
Comment 5 andreas.schluens 2008-05-30 08:44:09 UTC
as->mnasato: This task needs a lot or rework we cant do currently. So I set the
target to OOoLater now. If you find some developers on OOo which can do that job
I will support you.
Regards
Andreas
Comment 6 Rob Weir 2013-07-30 02:37:48 UTC
Reset assignee on issues not touched by assignee in more than 1000 days.