(This time to the mailing list, instead of just to Guillaume.) Hi Guillaume,
One small note: to make HTTPS easy to use for Windows darcs users, it is very handy to have it use the Windows certificate store. I was just curious and checked, and it seems like wreq on Windows does not currently supports this, since wreq depends on http-client-tls, which depends on x509-store, but not on x509-system which looks like it actually reads the Windows certificate store. So note that that would probably be a restriction: if one wants to use HTTPS with on Windows, one would have to explicitly store the certificate somewhere, which can be a hassle. (Where would that be with current darcs on Linux with libcurl, by the way? Configure libcurl's CA cert file name as described on http://curl.haxx.se/docs/sslcerts.html, using environment variable CURL_CA_BUNDLE?) But, of course, having _some_ HTTPS support for darcs on Windows is an improvement over having none at all. :-) And perhaps updating http-client-tls to use x509-store could be made part of the SoC project... Groetjes, <>< Marnix On Mon, Feb 9, 2015 at 6:22 PM, Guillaume Hoffmann <guilla...@gmail.com> wrote: > > Dear darcs'ers, > > this year's Summer of Code program starts son: by end of March, > student applications should be submitted to Google. We are probably > going to work again with students that have not contributed to darcs > before. > > Since two students in my university are interested about it, I'd like > to hear your comments about the following two project ideas I thought > of. > > > 1. HTTP system overhaul, a.k.a. "switch to wreq and see what happens". > This would involve having wreq (http://www.serpentine.com/wreq/) as > default download system, while leaving the current libcurl and HTTP > code for benchmarking purposes. > > The benefits would be: > > * no longer requiring separate compilation/installation of libcurl > * https support under windows (somehow we can't have libcurl under windows?) > * access to repositories behind http authentication (and probably > other benefits of wreq) > > Deliverables (apart from the code itself): > > * HTTP benchmarks (wreq vs libcurl vs HTTP) > * testing that pipelining actually works > * testing under windows / linux > > 2. Work towards Darcsden as a local UI and other improvements > > * plain files backend (vs current CouchDB) > * other stuff to help Darcsden be a local UI (without actually > involving any UI work)? any idea? > * unauthenticated patch submission via darcs send and http > > Apart from opinions about these project ideas, if someone thinks there > are more worthwile projects to do, please tell. > > > Guillaume > _______________________________________________ > darcs-users mailing list > darcs-users@darcs.net > http://lists.osuosl.org/mailman/listinfo/darcs-users -- Marnix Klooster marnix.kloos...@gmail.com -- Marnix Klooster marnix.kloos...@gmail.com
_______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
