> On Sun, 16 Oct 2005, S. Mike Dierken wrote:
> >
> > http://whatwg.org/specs/web-apps/current-work/#network
> >
> > My only question is - why?
>
> Imagine trying to play a game like Quake implemented in a Web
> page. You need bidirectional communication.
Okay. Outbound messages are obviously n
Ian Hickson wrote:
> On Sun, 16 Oct 2005, Matthew Raymond wrote:
>>[...] Also, my model doesn't allow menus to be displayed via a
>>hyperlink. Displaying menus via hyperlink would introduce weird
>>situations like bookmarking menus and referencing menus outside the
>>document. While it may be po
Ian Hickson wrote:
> On Sat, 8 Oct 2005, Matthew Raymond wrote:
>>My argument isn't that |title| can't contain pattern hints. What I
>>object to is designing HTML5 so that |title| is the only thing that can
>>be used for pattern hints on legacy browsers.
>
> I don't understand why you think it i
Rather than invent another protocol, this seems like an
excellent application for BEEP:
http://www.ietf.org/rfc/rfc3080.txt
Restricting connections to the originating host only has shown
to be fairly effective so far, and it's quite easy to see how
allowing arbitrary connections (no matter what
On Mon, 2005-10-17 at 05:27 +, Ian Hickson wrote:
> It's not intended to use port 80 only; where does it say that? That's an
> error. It is intended to be usable on ports 80, 443, and anything greater
> than 1024. (80 and 443 to attempt to tunnel out of psychotic firewalls,
ObFirewallsExistF
