2010/3/27 Rohit Vaidya <rohitvvv@xxxxxxxxx>: > The statement for gsoc 2010 ideas page mentions writing a api to replicate > similar functionality as cURL. > Does this simply mean a cURL implmentation in C++ ( a complete cURL rewrite > from scratch) or > writing a c++ wrapper and then extending an API. As far as I know, it is something like this, but the others might correct me: A wrapper can work in a first prototype (while developing), but I think Haiku devs expect something more fitting for Haiku. The code would probably need to be mostly written from scratch, but if the licensing permits using code from other projects should be ok. I think these are some of the wanted things: * The C++ API needs to be of the high standards we expect in Haiku. * It should be pluggable, being able to write protocol modules to support additional protocols * It should be able to replace cURL as the backend for the Haiku WebKit port. To look for inspiration I think these have been mentioned before: * Java Protocol handlers * Haiku Translation Kit ( http://www.haiku-os.org/legacy-docs/bebook/TheTranslationKit_Introduction.html ) - just for demonstrating how the pluggable part can work. (In Haiku a all graphics apps that uses the Translation Kit can support new formats when you add them as translators) * Chromium network code > How is cURL implementation done in haiku. Is it a 3rd party library or > completely rewritten in Haiku ? It's a 3rd party lib. /Fredrik Holmqvist, TQH