9 Feb
2011
9 Feb
'11
10:20 p.m.
On 2/9/2011 1:47 PM, Ted Hardie wrote:
But the fact that it is a *browser* who acts as a client should not be our focus. If an app on a mobile platform wants to use the same technologies, for example, that should be fine with us even if it is not a "browser".
However the fact that it must support the "browser" case does impose limitations that might not exist otherwise. An example is the requirement for an explicit handshake before sending UDP data towards a destination. People are very forgiving with what installed native apps can do, but not very happy when browsers load banner ads that do these sorts of things as a side-effect. Matthew Kaufman