Live data from Hacker News

W3C HTML JSON form submission

w3.org

101–103 of 103 posts

Re: W3C HTML JSON form submission

#101
post #88

Earlier quoted context omitted.

I've heard that before... https://en.wikipedia.org/wiki/XSLT

Isn't the Blizzard website largely written in XML and XSLT? I can imagine quite a few scenarios where that can be a good approach.

The WoW Armory website used to be written in XSLT on top of a horrendeous java stack. It's commonly referred to as the badmory and was slow as all hells. It had a pure-html fallback (rendered serverside into html) for unsupported browsers. It's one of the worst pieces of web I've ever seen... and I've seen some stuff.

It's no longer using all this, of course. They hired the guys from wowhead.com and had them redo the whole thing in a saner stack.

Re: W3C HTML JSON form submission

#103
post #47

I don't agree with Example 9, we should use data uri scheme for file content "files": [{ "name": "dahut.txt", "src": "data:text/plain;base64,REFBQUFBQUFIVVVVVVVVVVVVVCEhIQo=" }] http://en.wikipedia.org/wiki/Data_URI_scheme

1. Other form encoding types have discrete MIME type fields.

2. While data URIs are awesome, it forces you to process that URI in some way (parse, regex, whatever) just to get the MIME type. Also, this forces 13 bytes of redundancy every time.

Post reply on HN