I appreciate the conscientiousness about backward-compatibility here,
but, as a data point of one developer, I would be happy to incur the
backward-incompatibility of option #1 in exchange for getting rid of the
Cookbook HTTPS hack sooner rather than later.
I also think that Eli's option #1 could be done without breaking
backward-compatibility, but I'm not sure it's worth the effort in code
and documentation, and I don't want to discourage him moving forward
with #1 by making the task harder than it has to be.
(Full disclosure: Breaking backward-compatibility in the option #1 way
would generate approx. one billable hour of consulting work for me.
Just to edit some "require" forms, quickly inspect the call sites with
Emacs grep, test, and remove a Cookbook hack file from the CM branch.)
Thanks for tackling this, Eli.
Robby Findler wrote at 06/19/2011 06:26 PM:
I think we should not remove anything from the net/url library
(including the unitized interface) as I believe that will break old
code.
On Mon, Jun 20, 2011 at 5:57 AM, Eli Barzilay <e...@barzilay.org> wrote:
1. Looking at the code, there are only two tcp functions used
(`tcp-connect' and `tcp-abandon-port'), so eliminating the unit
interface and just hooking things up so that an "https" scheme uses
the ssl functions is relatively easy.
--
http://www.neilvandyke.org/
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
