Re: [whatwg] postMessage() issues

2008-04-21 Thread Jonas Sicking
Aaron Boodman wrote: On Wed, Apr 16, 2008 at 3:17 PM, Jonas Sicking [EMAIL PROTECTED] wrote: Maciej Stachowiak wrote: - Processing a reply synchronously is awkward in any case, since you need a callback. I'm not sure I follow this argument, I actually come to the opposite conclusion. Say

Re: [whatwg] postMessage() issues

2008-04-17 Thread Peter Kasting
On Wed, Apr 16, 2008 at 6:41 PM, Jonas Sicking [EMAIL PROTECTED] wrote: Peter Kasting wrote: I think the argument assumed you were communicating with a single frame in the common case, in which case the current API is more awkward than one in which the postMessage() call itself returns the

Re: [whatwg] postMessage() issues

2008-04-17 Thread Aaron Boodman
On Wed, Apr 16, 2008 at 3:17 PM, Jonas Sicking [EMAIL PROTECTED] wrote: Maciej Stachowiak wrote: - Processing a reply synchronously is awkward in any case, since you need a callback. I'm not sure I follow this argument, I actually come to the opposite conclusion. Say that a page is

Re: [whatwg] postMessage() issues

2008-04-17 Thread Aaron Boodman
On Thu, Apr 17, 2008 at 7:22 PM, Ojan Vafai [EMAIL PROTECTED] wrote: IMO, the tradeoff is still worth it, though. And in the future, with something like Hixie's messaging proposal, this problem will go away (because you'll have stateful objects that represent a conversation). I don't

Re: [whatwg] postMessage() issues

2008-04-16 Thread João Eiras
Hi! I agree with everything Maciej said, but I'm rather impartial. The word post implies posting something to a queue of messages, like we've seen in other programming APIs. There are use cases for both sync and async API, so we should support both. We could have either a new parameter for

Re: [whatwg] postMessage() issues

2008-04-16 Thread Jonas Sicking
So one thing I should note first of all is that the implementation that is currently in the Firefox 3 betas are synchronous. It is unlikely that we can get this changed by final shipping since we are more or less in code freeze already. Of course, we implemented this knowing that it's part of

Re: [whatwg] postMessage() issues

2008-04-16 Thread Peter Kasting
On Wed, Apr 16, 2008 at 3:17 PM, Jonas Sicking [EMAIL PROTECTED] wrote: - Processing a reply synchronously is awkward in any case, since you need a callback. I'm not sure I follow this argument, I actually come to the opposite conclusion. Say that a page is communicating with multiple

Re: [whatwg] postMessage() issues

2008-04-16 Thread Jonas Sicking
Peter Kasting wrote: On Wed, Apr 16, 2008 at 3:17 PM, Jonas Sicking [EMAIL PROTECTED] wrote: - Processing a reply synchronously is awkward in any case, since you need a callback. I'm not sure I follow this argument, I actually come to the opposite conclusion. Say

[whatwg] postMessage() issues

2008-04-15 Thread Ian Hickson
On Tue, 15 Apr 2008, Sunava Dutta wrote: Just following up to my email a few weeks back regarding cross document messaging. http://lists.w3.org/Archives/Public/public-html-comments/2008Feb/0024.html We'd love to know whether our proposed changes here (in the rewrite) can be accepted or