W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2013

Re: [whatwg] onclose events for MessagePort

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 1 Oct 2013 17:45:32 +0000 (UTC)
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Message-ID: <alpine.DEB.2.00.1310011736290.20189@ps20323.dreamhostps.com>
Cc: whatwg@lists.whatwg.org
On Tue, 1 Oct 2013, Boris Zbarsky wrote:
> On 10/1/13 12:58 PM, Ian Hickson wrote:
> > If the browser crashes, it's not going to be able to send messages 
> > anyway
> 
> This concept of "the browser"...
> 
> The situation being considered here is that you have two web pages in 
> two different OS-level processes that have a MessageChannel between 
> them.  One of the OS-level processes crashes (and hence obviously can't 
> send any more messages, as you note).  The other one would like to know 
> that its counterparty is gone.  How should it find out?  That's the 
> problem I think Ehsan is trying to solve.

Crashing is non-conforming. Having features explicitly to handle the 
non-conforming case is a bit weird. :-)

How often are we really expecting one tab to be talking to another tab, 
and then that tab crashes, and the author was able to prepare code to 
handle that gracefully, in a production environment?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 1 October 2013 17:45:56 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:11 UTC