mbien commented on PR #8024: URL: https://github.com/apache/netbeans/pull/8024#issuecomment-2855543809
to reschedule there must be a failure first. I am just curious if there is any evidence for failures on set or get still - post JDK fixes. Keep in mind the async mechanism was originally a workaround for a different problem: very slow response time in some cases. The loop happened later as patch on the patch. IMO: the loop is more questionable than the async mechanism given that Clipboard is expected to throw ISA https://docs.oracle.com/en/java/javase/24/docs/api/java.datatransfer/java/awt/datatransfer/Clipboard.html#setContents(java.awt.datatransfer.Transferable,java.awt.datatransfer.ClipboardOwner) if it doesn't work -> throw. If get needs to be async its null (or last item) instead of exception. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For additional commands, e-mail: notifications-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
