The intent of the spec is fairly clear that addEventListener("message") should not start the message queue dispatch - only setting the onmessage attribute does that:<div><br></div><div><span class="Apple-style-span" style="background-color: rgb(238, 238, 238); font-family: sans-serif, 'Droid Sans Fallback'; font-size: medium; line-height: 21px; ">The first time a <code style="font-size: inherit; font-family: monospace, 'Droid Sans Fallback', sans-serif; font-variant: normal; color: rgb(255, 69, 0); "><a href="#messageport" style="color: inherit; background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: transparent; background-position: initial initial; background-repeat: initial initial; ">MessagePort</a></code> object's <code title="handler-MessagePort-onmessage" style="font-size: inherit; font-family: monospace, 'Droid Sans Fallback', sans-serif; font-variant: normal; color: rgb(255, 69, 0); "><a href="#handler-messageport-onmessage" style="color: inherit; background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: transparent; background-position: initial initial; background-repeat: initial initial; ">onmessage</a></code> IDL attribute is set, the port's <a href="#port-message-queue" style="color: rgb(0, 0, 204); background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: transparent; background-position: initial initial; background-repeat: initial initial; ">port message queue</a> must be enabled, as if the <code title="dom-MessagePort-start" style="font-size: inherit; font-family: monospace, 'Droid Sans Fallback', sans-serif; font-variant: normal; color: rgb(255, 69, 0); "><a href="#dom-messageport-start" style="color: inherit; background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: transparent; background-position: initial initial; background-repeat: initial initial; ">start()</a></code> method had been called.</span><br>
<div><br></div><div>In fact, the only reason for the existence of the MessagePort.start() method is to enable applications to start message queue dispatch when using addEventListener().</div><div><br></div><div>I don't have a strong opinion as to whether we should change the spec, though. I suspect not, given Anne's email. We should instead change the example in the workers spec to call start().</div>
<div><br></div><div>-atw</div><div><br><div class="gmail_quote">On Tue, Sep 29, 2009 at 2:13 AM, Anne van Kesteren <span dir="ltr"><<a href="mailto:annevk@opera.com">annevk@opera.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, 29 Sep 2009 09:13:17 +0200, Zoltan Herczeg <<a href="mailto:zherczeg@inf.u-szeged.hu" target="_blank">zherczeg@inf.u-szeged.hu</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Anyway, my qestion is:<br>
- should addEventListener enable message transmitting?<br>
- Should it do it in all cases, or only when "message" is passed as the<br>
first argument<br>
</blockquote>
<br></div>
I don't think it should. Web Workers should not modify the semantics of addEventListener.<br><font color="#888888">
<br>
<br>
-- <br>
Anne van Kesteren<br>
<a href="http://annevankesteren.nl/" target="_blank">http://annevankesteren.nl/</a><br>
</font></blockquote></div><br></div></div>