javascript - Why does the SharedWorker onConnect event have a Ports array? - Stack Overflow

admin管理员组

文章数量:1391960

In all examples I've seen, they're similar to this

onconnect = function(e) {
    var port = e.ports[0];

    port.onmessage = function(e) {
        var workerResult = 'Result: ' + (e.data[0] * e.data[1]);
        port.postMessage(workerResult);
    }

    port.start();
}

Is there an instance where the ports array will ever have more than one element? Using chrome://inspect on the SharedWorker and printing out e, I get

regardless of how many instances are spawned sharing the SharedWorker, where the length is always 1. Why isn't it just a MessageEvent instead of an array? What use case is there for it to be an array?

In all examples I've seen, they're similar to this

onconnect = function(e) {
    var port = e.ports[0];

    port.onmessage = function(e) {
        var workerResult = 'Result: ' + (e.data[0] * e.data[1]);
        port.postMessage(workerResult);
    }

    port.start();
}

Is there an instance where the ports array will ever have more than one element? Using chrome://inspect on the SharedWorker and printing out e, I get

regardless of how many instances are spawned sharing the SharedWorker, where the length is always 1. Why isn't it just a MessageEvent instead of an array? What use case is there for it to be an array?

• javascript
• web-worker
• shared-worker

Share Improve this question Follow edited Jun 20, 2020 at 9:12 CommunityBot 111 silver badge asked Sep 6, 2016 at 7:43 No_nameNo_name 2,82033 gold badges3434 silver badges4949 bronze badges

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 8

The reason is that it reuses the MessageEvent interface which can sometimes be dispatched with an array of multiple ports. That's all.

本文标签： javascriptWhy does the SharedWorker onConnect event have a Ports arrayStack Overflow