After reading through the README, my vote is for a new "web-server2" collection and keep web-server frozen as is except to fix bugs.
The compatibility issues simply appear to be much more than an explicit make-xexpr-response call and will most likely cause breakage. This is the type of change that two parallel versions should be kept until it's clear everyone has a chance to migrate (and that can take a long while). I like the migration path from mzscheme to scheme to racket that all are still available and maintained. Except for the mutable pair issue that broke a few libraries, it was quite well managed. Cheers, yc On Fri, Dec 3, 2010 at 10:54 PM, Jay McCarthy <jay.mccar...@gmail.com>wrote: > Here is my current plan: > > Add web-server/compat/0 directory with, e.g., > web-server/compat/0/http/response-structs to hold compatibility bindings to > bridge the old http/response-structs and the new http/response-structs > > In that directory is the attached README. > > What do you think? > > Jay >
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
