Switching to ByteString does not break windows applications. WAI can be perfectly used on windows for development, testing, even production use unless you are building next Facebook :) In order to see considerable degradation in performance from switching to ByteString on windows, your web application really need to have a huge traffic. But then again why would you host it on windows in this case ? On Friday, June 15, 2012 03:03:06 PM Thomas Hartman wrote:

I don't go anywhere near windows, but I disagree anyway.

Making it possible for windows users to at least test this out is a potentially significant factor in adoption.

The other frameworks play nicely with windows. WAI should too.

On Fri, Jun 15, 2012 at 3:00 PM, Vagif Verdi wrote:

...

Considering that we are talking about the web server, it would be safe to assume that most people would not run it on windows for production use.

So i say WAI should switch to ByteString, and let the windows users be penalized just a little bit. You can't please everyone.

On Friday, June 15, 2012 02:47:15 PM Johan Tibell wrote:

...

On Fri, Jun 15, 2012 at 2:41 PM, Greg Weber wrote:

...

The ticket would be to switch the standard libraries to use system-filepath, which probably requires a mailing list discussion somewhere, a lot of boring changes of code, and a more inconvenient API for end users. I will wait for Text to become standardized first

:)

The FilePath issue has been discussed at length before. The problem is that different OS:es define file paths to be different things (i.e. Unicode or bytes.) The FilePath type somehow has to bridge that, that will be difficult. My main grip with FilePath right now is that it's not an abstract type.

-- Johan

_______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel

_______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel