Experimental IRC log happs-2007-11-02

Available formats: content-negotiated html turtle (see SIOC for the vocabulary)

Back to channel and daily index: content-negotiated html turtle

These logs are provided as an experiment in indexing discussions using IRCHub.py, Irc2RDF.hs, and SIOC.

19:04:15<kaol>can happs cache XML?
19:04:39<kaol>I've been thinking... It's possible to include one XML file from another.
19:05:18<kaol>I could put more static bits of the site on a cached XML file and just generate as little as I could
19:05:58<kaol>people do silly stuff like cache HTML pages too. I'm sure you could do better than that.
19:06:42<kaol>it's possible to put XML on a static file and serve that, already, but it'd be nice to not have to do it quite that manually
19:07:38<shapr>What would be a good way to memoize it?
19:07:42<shapr>Can xsltproc already do that?
19:10:10<kaol>Why'd it involve xsltproc? It's not involved with browsers that do XSLT by themselves, right?
19:11:40<kaol>I wish I were familiar with happs 0.9.1. I could tell just what would be involved with doing stuff like this.
19:14:19<kaol>turning haskell into XML can't be quite cost free. Outputting data as strings is always icky.
19:15:36<kaol>ACTION has no idea if he's even making any sense with this idea
19:15:52<shapr>HAppS turns the application state into xml, xsltproc processes that data according to the xslt files.
19:16:17<kaol>I hope not unconditionally
19:16:40<shapr>?
19:16:41<kaol>firefox has been able to do xslt on client side since forever and IE too
19:16:59<kaol>that's a major selling point of XSLT
19:17:24<kaol>to turn the data into representation on client side
19:17:44<kaol>xsltproc is only fallback for those cases when the client can't do it. I hope.
19:18:26<shapr>I know that used to be the only way HAppS did markup, I don't know if HAppS still does that though.
19:18:26<shapr>Lemmih: Do you know if client side xslt still works?
19:21:34<kaol>client side xslt should be easy. just return the XML and let it do it.
19:21:59<kaol>the trick is to guess from the user agent string when that's not supported and give the HTML if so
19:36:05<Lemmih>HAppS is horrible at understanding user agents.
19:37:14<kaol>I wouldn't mind serving XML all the time, in my own use...
19:41:39<Lemmih>HAppS never enforced any particular coding style.
19:42:19<earthy>why is HAppS horrible at understanding user agents?
19:42:34<kaol>I wish the HTTP headers had something that would tell the server right away that they can do XSLT. Guessing it from the ua string is suboptimal.
19:42:39<earthy>it should have access to the entire HTTP header, right?
19:43:09<Lemmih>earthy: It uses a simple regex to check for lynx and some other browser.
19:43:21<Lemmih>earthy: There's no reason it couldn't do it better.

Back to channel and daily index: content-negotiated html turtle