Closed Bug 9619 Opened 25 years ago Closed 25 years ago

sched: Linux clipboard Streams for large data sets

Categories

(Core :: XUL, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: trudelle, Assigned: pavlov)

References

Details

(Whiteboard: i am pretty sure this works. waiting for a test case to verify.)

Linux clipboard Streams for large data sets (test & verify) 0.5d pavlov 0%
Assignee: trudelle → pavlov
assigning to pavlov
Status: NEW → ASSIGNED
Target Milestone: M9
adding pinkerton so he can tell me what i'm supposed to do
/me is confused and summarily unhelpful here.
Rod? Do you know what the stream part of this is? GTK magically handles large data by using the standard X incr protocol with selection.. i'm not really sure how this works, but it is handled for us, so I don't have to worry with it.
I would assume that the streams part regards using an nsIStream interface instead of an nsString for large data sets, so that the whole thing doesn't have to be read into memory (streaming inside the X server won't help this if you're streaming it all into one big nsString). But I don't actually see any stream-based interfaces in nsIClipboard or nsITransferable, so maybe this actually means something else.
It wasn't that we were going to stream it in so it wouldn't have to be in memory, at least that wasn't where we thought we needed to go. We just didn't want to keep large pieces of clipboard data in memory for long periods of time. Like someone doing a large copy and then doing nothing with for quite a while. I have implemented in XP code in the transferable. It still needs to be tested on the Mac and UNIX.
Blocks: 9639
does anyone have large data i can test with?
Whiteboard: i am pretty sure this works. waiting for a test case to verify.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
rods said: > Go into nsTransferable.cpp at the top are these lines: > > // million bytes > #define LARGE_DATASET_SIZE 1000000 > //#define LARGE_DATASET_SIZE 10 > > Comment out the larger one and uncomment out the other one, this will force > virtually all clipboard operations to be cached to disk. Then try a simple > copy/paste. so i do this, and it works. so i'm marking this fixed.
Status: RESOLVED → VERIFIED
code level fix, marking verified. reopen if i'm wrong here...
You need to log in before you can comment on or make changes to this bug.