Bug 361487 - Stream Files instead of creating local copy
Summary: Stream Files instead of creating local copy
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.24.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-04-07 08:48 UTC by Richard Llom
Modified: 2018-10-27 04:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Llom 2016-04-07 08:48:20 UTC
I have pdf's on a local NAS which I access via smb (or ftp - behavior is the same) with dolphin.

When I click on a pdf, first of all copy dialog appears and then okular opens the local copy.
This has several disadvantages:
- Unnecessary slow (one has to wait for the copy of the whole file, instead of an instant open)
- It is not possible to see changes on the pdf file by reloading (F5)
- Unnecessary local disk usage / fragmentation, etc
- Unnecessary UI clutter/popups/notification (Copy dialog, examination finished, etc.)

So I propose that okular should "stream" the file from the NAS server, instead of creating a local copy.

This is the open command for pdfs in my file type properties:
"okular %U %i -caption %c"
Comment 1 Albert Astals Cid 2016-04-07 21:40:19 UTC
> It is not possible to see changes on the pdf file by reloading (F5)
You mean that if you open a file on smb and press F5 it doesn't reload the file?
I guess that's because dolphin does that not because okular does it right?
i.e. if you call okular from the command line it will work, no?
Comment 2 Richard Llom 2016-04-08 00:41:54 UTC
(In reply to Albert Astals Cid from comment #1)
> > It is not possible to see changes on the pdf file by reloading (F5)
> You mean that if you open a file on smb and press F5 it doesn't reload the
> file?
I just checked and indeed Okular does loads a new (changed) copy of that file.

> I guess that's because dolphin does that not because okular does it right?
I do not understand this sentence.

> i.e. if you call okular from the command line it will work, no?
It is the same behavior (okular creates local copy of pdf file).
Comment 3 Albert Astals Cid 2016-05-11 22:33:03 UTC
> > i.e. if you call okular from the command line it will work, no?
> It is the same behavior (okular creates local copy of pdf file).
You need a local copy, if you don't have a local copy it means you either have to
A) have the file in memory forever, which is bad if the file is big.
B) access the remote server every time you need to read the file, e.g. rendering a new page, which is bad because you create extra traffic and is dependent on the remote server disappearing.

So a local copy is the best thing to do, no?
Comment 4 Richard Llom 2016-05-20 13:45:17 UTC
Well, IMHO memory is plenty.
And as long as the file is open in okular, isn't it anyways in cache/memory or does it load from disk for each new page?

Still when using a local copy, would it be possible to:
a) open the file instantaneous (after the first 100kb downloaded) - INSTEAD of waiting for the whole file to download?
b) Have the whole copy and examinating pop-ups hidden from the user?

Ty
Comment 5 Andrew Crouthamel 2018-09-26 22:07:42 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 04:20:52 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!