Re: [Haskell-cafe] Re: [web-devel] Google Summer of Code: BlazeHTML RFC

Hey Thomas, Yes, hsx/hsp could get a performance gain by using BlazeHtml as a backend. However, I'm not sure if it is possible to change the backend without changing the user API (but I do hope so). Kind regards, Jasper Van der Jeugt On Sun, May 30, 2010 at 5:58 PM, Thomas Hartman wrote:

I'm a heavy hsp user. Could hsp benefit from this project by using blaze as a back end instead of whatever it's using now?

IIUC, Hsp uses hsx (via the preprocessor program trhsx) to convert xml-containing hybrid hsp/xml/html files into compilable haskell.

I expected hsx uses XHTML (which iiuc is what blaze would replace) on the backend but I don't see it listed in the dependencies at

http://hackage.haskell.org/package/hsx-0.7.0

so I guess it doesn't and uses something internal rather than xhtml. (Right?)

My question as regards BlazeHTML is if there could be any performance win/tie in for the hsp/hsx toolchain.

FWIW, wrt to blaze sclv commented on reddit "The idea is rather that this would be a replacement for the html combinator library, as distinct from templating (hamlet, hstringtemplate, bravo, chunks, press, & co) and as distinct from the *sp model of inlined code (hsp).

Edit: Ideally, and generally for Haskell libs, the choices of persistence layer, html generation library, dispatch model, and server layer are largely orthogonal. Strong typing makes any ad-hoc plumbing a breeze."

http://www.reddit.com/r/haskell/comments/bxa0a/blazehtml_a_blazingly_fast_ht...

thomas.

2010/5/30 Tom Lokhorst :

...

+1 for HTML5.

Also, I suggest focussing on the html serialization of HTML5.

The xml serialization (XHTML5) is only useful in an XML environment. For such environments pure xml libraries are more appropriate.

Besides, I like html syntax better.

On 30 May 2010 16:27, Jochem Berndsen wrote:

...

On 05/29/2010 08:05 PM, Gregory Collins wrote:

...

Matt Parker  writes:

...

    Q3: Which HTML version would you preferably use?

HTML 5. google summer of code should be about pushing the new and exciting.

Yes, definitely, this should be the default IMO.

+1

-- Jochem Berndsen | jochem@functor.nl _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe