Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8253546

Explore using AWT EventQueue dispatch thread as carrier thread

    Details

    • Type: Task
    • Status: In Progress
    • Priority: P2
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: client-libs
    • Labels:

      Description

      This task tracks exploring the implications of a custom scheduler that uses the AWT EventQueue dispatch thread as the (single) carrier thread, e.g.

      Thread.builder().virtual(EventQueue::invokeLater).task(() -> { ... }).start();

      Would it be feasible to create a "bouncing balls" application where each component is control by a virtual thread? Answering that might help tease out the challenges/issues. It may be that EventQueue. isDispatchThread() or its usages will need to be re-examined or maybe new APIs will be needed to allow the AWT implication test if the underlying thread is the EDT.

        Attachments

          Activity

            People

            • Assignee:
              serb Sergey Bylokhov
              Reporter:
              alanb Alan Bateman
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: