From john at smadness.com Wed Aug 4 13:55:42 2010 From: john at smadness.com (john gale) Date: Wed, 4 Aug 2010 13:55:42 -0700 Subject: [imps] setting up, and keeping up, the html5 validator.nu java servlet Message-ID: <6CDBC4B3-017F-451D-B2C8-56B58E3E435C@smadness.com> Hi ~ I succeeded in setting up the standalone html5 validator.nu java servlet on Mac OS X Server 10.6 (SnowLeopard) in concert with a checked out copy of the W3C validator. Things seem to work well. I'd like to keep the webserver running automatically, and I'm trying to find the most reliable way to do so. Running the "python build/build.py run" command starts up the java server, but it seems to exit as soon as return is pressed in the terminal window. Additionally, the python process seems to start and replace itself with the java process which causes setting up a launchd (cron-like) job to keep it running futile, since launchd sees the python process exit and tries to restart it. Is there a recommended way of making the java webserver start at login, and continue running in the background? launchd is the most supported way to go on Mac OS X, but something in the java code is quitting itself, possibly when it realized there's no STDIN, or something in the launchd environment is being hostile to the servlet keeping itself running. A launchd plist shoved into /Library/LaunchDaemons doesn't keep the servlet running, and the KeepAlive launchd plist flag just continuously restarts the process every few seconds. There are no real log messages anywhere, which is what's making me think the java servlet is quitting itself because of something in its environment. thanks, ~ john From ian at hixie.ch Mon Aug 9 17:03:20 2010 From: ian at hixie.ch (Ian Hickson) Date: Tue, 10 Aug 2010 00:03:20 +0000 (UTC) Subject: [imps] 24 June 2010 HTML 5 spec: bug when emitting tokenizer start tags In-Reply-To: <2116943659.538426.1277364929829.JavaMail.root@cm-mail03.mozilla.org> References: <2116943659.538426.1277364929829.JavaMail.root@cm-mail03.mozilla.org> Message-ID: On Wed, 23 Jun 2010, Rob Jellinghaus wrote: > > The 24 June 2010 working draft of the HTML5 spec has, I believe, a bug > with tokenizer state update when emitting start tags. The bug is an > ordering problem between the tokenizer state update performed by the > tokenizer itself, and the tokenizer state update sometimes performed by > the tree construction stage. > > http://dev.w3.org/html5/spec/Overview.html currently links to > http://www.w3.org/TR/2010/WD-html5-20100624/ as the latest version, but > the latter link is broken at the moment. Looking at the former, for > instance: > > Section 8.2.4.10 (Tag name state) says > > ?U+003E GREATER-THAN SIGN (>) > Emit the current tag token. Switch to the data state. > > The "Emit the current tag token" step is defined in section 8.2.4 as: > > When a token is emitted, it must immediately be handled by the > tree construction stage. The tree construction stage can affect > the state of the tokenization stage, and can insert additional > characters into the stream. > > So let us consider the following HTML: > > > > > > > > > At the closing '>' of ' > > > > > At the closing '>' of ' > > > > > At the closing '>' of '