[Mono-list] Should I Forking HttpListener?

jbcooley jbcooley at tuxinthebox.net
Thu Nov 27 10:42:03 EST 2008

I need to read from the request stream even on GET and disable chunking when
no ContentLength64 is specified.  It's a few small changes to
HttpListenerRequest, HttpConnection, and HttpListenerResponse.  The changes
are necessary to support a non-standard HTTP protocol for TiVo applications.

I've extracted the HttpListener and all dependent classes into a new
assembly for testing purposes.  Part of the process of extracting the
classes required changes to the namespace.  Is there an alternative to
forking the code that anyone would recommend?  I'm fine with contributing
the changes back, but I don't think they would be generally useful.

If I do proceed with a fork, I'll need a new namespace and assembly name. 
I'm considering Mono.Net for the namespace and Mono.HttpListener for the
assembly name.  Considering the non-standard behavior of my altered
HttpListener should choose a name that does not include Mono to avoid
confusion with the standard class?

View this message in context: http://www.nabble.com/Should-I-Forking-HttpListener--tp20721045p20721045.html
Sent from the Mono - General mailing list archive at Nabble.com.

More information about the Mono-list mailing list