Re: [w3c/clipboard-apis] Support for delayed clipboard data (#41)

I see that remote chrome is already mentioned here, but I'd like to add to that that there are many other remote desktop protocols (RDP, VNC, Spice, etc.) that could all benefit from not having to transfer the data whenever the clipboard changes.

The user will in most cases not even use the clipboard so there will be a lot of wasted bandwidth. Bandwidth that could have been used for transferring image updates instead.

It would be nice if this could be added before the async API is finalised.

(This also affects DragEvent and ClipboardEvent, although it's probably rare that their inefficiency is a problem)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/issues/41#issuecomment-375278464

Received on Thursday, 22 March 2018 11:55:47 UTC