Re: [apps-discuss] Last Call for HTML5 in the W3C

That is the API perspective. That would also make the ABI perspective 
regard HTTP status codes 200, 201, 202, and 203 as standard input, 
output, error, and one bit "control flow" where TLS does not exist in 
SI/SO modes.

Note that "network order" considers top three bits, yet that is not 
clear about top three of each byte or the thee most significant bits of 
the last byte. That standard creates this kind of mask:
100000001000000011111000

Can we just default something like the OAuth MAC header to that code to 
signify that mask is known? Then, check /.well-known/ for that bitstream?

We can then determine the queue direction.

On 06/17/2011 01:45 PM, Mark Nottingham wrote:
> [ with my IETF/W3C Liaison hat on ]
>
> The W3C has announced a Last Call on the HTML5 specification; see:
>   http://www.w3.org/2011/02/htmlwg-pr.html
>
> The IETF has been encouraged to provide feedback, especially regarding HTML's use of and interface with IETF technologies.
>
> For background on Last Call in their process, see:
>   http://www.w3.org/2005/10/Process-20051014/tr.html#last-call
>
> and the specification itself:
>   http://www.w3.org/TR/html5/
> paying special attention to the 'status of this document' section for information about the Last Call and how to provide feedback.
>
> See also their LC FAQ:
>   http://www.w3.org/2011/05/html5lc-faq.html
>
> Cheers,
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>    

-- 
--- http://twitter.com/Dzonatas_Sol ---
Web Development, Software Engineering
Ag-Biotech, Virtual Reality, Consultant