This is an anonymzed summary of the survey results. Full results of this questionnaire are available only to the W3C Team.
This questionnaire was open from 2003-09-01 to 2003-09-30.
42 answers were received.
| Choice | All responders |
|---|---|
| Results | |
| yes | 27 |
| no | 14 |
| Responder | 1.1 Do you develop or have you developed applications that use libwww? |
|---|---|
| Anonymous Responder 1 | yes |
| Anonymous Responder 2 | yes |
| Anonymous Responder 3 | yes |
| Anonymous Responder 4 | no |
| Anonymous Responder 5 | yes |
| Anonymous Responder 6 | yes |
| Anonymous Responder 7 | yes |
| Anonymous Responder 8 | yes |
| Anonymous Responder 9 | yes |
| Anonymous Responder 10 | yes |
| Anonymous Responder 11 | no |
| Anonymous Responder 12 | no |
| Anonymous Responder 13 | yes |
| Anonymous Responder 14 | no |
| Anonymous Responder 15 | yes |
| Anonymous Responder 16 | no |
| Anonymous Responder 17 | yes |
| Anonymous Responder 18 | no |
| Anonymous Responder 19 | yes |
| Anonymous Responder 20 | yes |
| Anonymous Responder 21 | yes |
| Anonymous Responder 22 | no |
| Anonymous Responder 23 | no |
| Anonymous Responder 24 | yes |
| Anonymous Responder 25 | yes |
| Anonymous Responder 26 | yes |
| Anonymous Responder 27 | yes |
| Anonymous Responder 28 | yes |
| Anonymous Responder 29 | yes |
| Anonymous Responder 30 | yes |
| Anonymous Responder 31 | yes |
| Anonymous Responder 32 | no |
| Anonymous Responder 33 | yes |
| Anonymous Responder 34 | yes |
| Anonymous Responder 35 | no |
| Anonymous Responder 36 | no |
| Anonymous Responder 37 | yes |
| Anonymous Responder 38 | no |
| Anonymous Responder 39 | no |
| Anonymous Responder 40 | |
| Anonymous Responder 41 | yes |
| Anonymous Responder 42 | no |
| Choice | All responders |
|---|---|
| Results | |
| Open source | 7 |
| Commercial | 12 |
| Tools used at work | 16 |
| Responder | Open source | Commercial | Tools used at work | Other |
|---|---|---|---|---|
| Anonymous Responder 1 | 1 | |||
| Anonymous Responder 2 | 1 | |||
| Anonymous Responder 3 | 1 | |||
| Anonymous Responder 4 | ||||
| Anonymous Responder 5 | 1 | |||
| Anonymous Responder 6 | 1 | |||
| Anonymous Responder 7 | 1 | It will be commercial if its performance is acceptable | ||
| Anonymous Responder 8 | 1 | |||
| Anonymous Responder 9 | 1 | |||
| Anonymous Responder 10 | 1 | |||
| Anonymous Responder 11 | ||||
| Anonymous Responder 12 | ||||
| Anonymous Responder 13 | 1 | |||
| Anonymous Responder 14 | ||||
| Anonymous Responder 15 | 1 | 1 | 1 | Lab implementations for academic research projects. |
| Anonymous Responder 16 | ||||
| Anonymous Responder 17 | 1 | |||
| Anonymous Responder 18 | I have used it as a reference example. | |||
| Anonymous Responder 19 | 1 | |||
| Anonymous Responder 20 | 1 | The application is used to provide a commercial service, the application software itself is not distributed to customers. The | ||
| Anonymous Responder 21 | 1 | |||
| Anonymous Responder 22 | Not applicable | |||
| Anonymous Responder 23 | 1 | 1 | ||
| Anonymous Responder 24 | 1 | |||
| Anonymous Responder 25 | 1 | |||
| Anonymous Responder 26 | 1 | 1 | 1 | We write Open Source software commercially. This question makes it appear as if commercial application preclude source release. |
| Anonymous Responder 27 | 1 | |||
| Anonymous Responder 28 | ||||
| Anonymous Responder 29 | 1 | 1 | 1 | |
| Anonymous Responder 30 | 1 | |||
| Anonymous Responder 31 | 1 | |||
| Anonymous Responder 32 | ||||
| Anonymous Responder 33 | 1 | |||
| Anonymous Responder 34 | 1 | |||
| Anonymous Responder 35 | ||||
| Anonymous Responder 36 | ||||
| Anonymous Responder 37 | 1 | 1 | ||
| Anonymous Responder 38 | ||||
| Anonymous Responder 39 | ||||
| Anonymous Responder 40 | ||||
| Anonymous Responder 41 | 1 | |||
| Anonymous Responder 42 |
| Responder | Comments |
|---|---|
| Anonymous Responder 1 | |
| Anonymous Responder 2 | Progress Software web services client transport (to be released) |
| Anonymous Responder 3 | Utility to import and export Power System Models based on the Common Information Model (CIM). The utility uses the liwww RDF parser. |
| Anonymous Responder 4 | |
| Anonymous Responder 5 | |
| Anonymous Responder 6 | |
| Anonymous Responder 7 | |
| Anonymous Responder 8 | We use libwww as a component in our html screen scraping tool set. You can get an idea of what we do at www.bcftech.com |
| Anonymous Responder 9 | Netcool/OMNIbus http://www.micromuse.com |
| Anonymous Responder 10 | Jigsaw Download (jigdo) http://atterer.net/jigdo/ |
| Anonymous Responder 11 | |
| Anonymous Responder 12 | |
| Anonymous Responder 13 | |
| Anonymous Responder 14 | |
| Anonymous Responder 15 | http://sourceforge.net/projects/mctk http://www.semagix.com/technology.html http://aisun0.ai.uga.edu/~bancroft/ |
| Anonymous Responder 16 | |
| Anonymous Responder 17 | Internal support for Web access for Delphi Internet (1995). |
| Anonymous Responder 18 | |
| Anonymous Responder 19 | |
| Anonymous Responder 20 | http://www.catbird.com, Catbird Networks |
| Anonymous Responder 21 | Amaya http://www.w3.org/Amaya/ |
| Anonymous Responder 22 | Not applicable |
| Anonymous Responder 23 | teTeX is a "standard" *nix installation of "TeX and friends" which I use everyday in my work. This comes with the "xdvi" dvi file viewer that has support for hyperlinked dvi files using libwww. The URL for tetex is http://www.tug.org/tetex The URL for xdvi is http://math.berkeley.edu/~vojta/xdvi.html |
| Anonymous Responder 24 | |
| Anonymous Responder 25 | |
| Anonymous Responder 26 | |
| Anonymous Responder 27 | WAP-Voyager (WAP-Gateway, http://www.ic3s.de) |
| Anonymous Responder 28 | |
| Anonymous Responder 29 | |
| Anonymous Responder 30 | |
| Anonymous Responder 31 | |
| Anonymous Responder 32 | |
| Anonymous Responder 33 | |
| Anonymous Responder 34 | http://www.avaya.com 4620 Web Browser |
| Anonymous Responder 35 | |
| Anonymous Responder 36 | |
| Anonymous Responder 37 | Amaya, in particular an IDN extension for libwww/Amaya |
| Anonymous Responder 38 | |
| Anonymous Responder 39 | http://www.mozilla.org |
| Anonymous Responder 40 | |
| Anonymous Responder 41 | |
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| Unix (Includes Linux, Solaris, BSD, QNX, ...) | 25 |
| Win32 (Includes Windows 9x, NT, 200x. XP, ...) | 17 |
| GTK | 4 |
| Responder | Unix (Includes Linux, Solaris, BSD, QNX, ...) | Win32 (Includes Windows 9x, NT, 200x. XP, ...) | GTK | Comments |
|---|---|---|---|---|
| Anonymous Responder 1 | 1 | |||
| Anonymous Responder 2 | 1 | 1 | ||
| Anonymous Responder 3 | 1 | 1 | ||
| Anonymous Responder 4 | ||||
| Anonymous Responder 5 | 1 | MacOS 9, MacOS X | ||
| Anonymous Responder 6 | 1 | 1 | ||
| Anonymous Responder 7 | 1 | 1 | ||
| Anonymous Responder 8 | 1 | 1 | ||
| Anonymous Responder 9 | 1 | 1 | Did not use libwww for the win32 version | |
| Anonymous Responder 10 | 1 | 1 | 1 | I have made my own MinGW-based port of libwww to Windows available. |
| Anonymous Responder 11 | ||||
| Anonymous Responder 12 | ||||
| Anonymous Responder 13 | 1 | |||
| Anonymous Responder 14 | ||||
| Anonymous Responder 15 | 1 | 1 | ||
| Anonymous Responder 16 | ||||
| Anonymous Responder 17 | 1 | Original code running on VMS. | ||
| Anonymous Responder 18 | portable command line is best. | |||
| Anonymous Responder 19 | 1 | |||
| Anonymous Responder 20 | 1 | |||
| Anonymous Responder 21 | 1 | 1 | 1 | |
| Anonymous Responder 22 | 1 | |||
| Anonymous Responder 23 | 1 | |||
| Anonymous Responder 24 | 1 | 1 | ||
| Anonymous Responder 25 | 1 | 1 | ||
| Anonymous Responder 26 | 1 | 1 | ||
| Anonymous Responder 27 | 1 | |||
| Anonymous Responder 28 | ||||
| Anonymous Responder 29 | 1 | 1 | ||
| Anonymous Responder 30 | 1 | |||
| Anonymous Responder 31 | 1 | |||
| Anonymous Responder 32 | ||||
| Anonymous Responder 33 | 1 | 1 | ||
| Anonymous Responder 34 | 1 | vxWorks RTOS | ||
| Anonymous Responder 35 | ||||
| Anonymous Responder 36 | ||||
| Anonymous Responder 37 | 1 | unix version needs some more tweaking | ||
| Anonymous Responder 38 | ||||
| Anonymous Responder 39 | 1 | 1 | ||
| Anonymous Responder 40 | ||||
| Anonymous Responder 41 | 1 | |||
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| C | 22 |
| C++ | 14 |
| Responder | C | C++ | Comments |
|---|---|---|---|
| Anonymous Responder 1 | 1 | 1 | |
| Anonymous Responder 2 | 1 | 1 | |
| Anonymous Responder 3 | 1 | ||
| Anonymous Responder 4 | |||
| Anonymous Responder 5 | 1 | ||
| Anonymous Responder 6 | i use Perl LWP | ||
| Anonymous Responder 7 | 1 | ||
| Anonymous Responder 8 | 1 | 1 | |
| Anonymous Responder 9 | 1 | 1 | |
| Anonymous Responder 10 | 1 | 1 | |
| Anonymous Responder 11 | |||
| Anonymous Responder 12 | |||
| Anonymous Responder 13 | 1 | ||
| Anonymous Responder 14 | |||
| Anonymous Responder 15 | 1 | 1 | |
| Anonymous Responder 16 | |||
| Anonymous Responder 17 | 1 | ||
| Anonymous Responder 18 | 1 | ||
| Anonymous Responder 19 | 1 | ||
| Anonymous Responder 20 | 1 | ||
| Anonymous Responder 21 | 1 | ||
| Anonymous Responder 22 | Not applicable | ||
| Anonymous Responder 23 | 1 | ||
| Anonymous Responder 24 | Coldfusion | ||
| Anonymous Responder 25 | 1 | 1 | |
| Anonymous Responder 26 | |||
| Anonymous Responder 27 | 1 | ||
| Anonymous Responder 28 | |||
| Anonymous Responder 29 | 1 | 1 | |
| Anonymous Responder 30 | 1 | ||
| Anonymous Responder 31 | 1 | ||
| Anonymous Responder 32 | |||
| Anonymous Responder 33 | 1 | ||
| Anonymous Responder 34 | 1 | 1 | |
| Anonymous Responder 35 | |||
| Anonymous Responder 36 | |||
| Anonymous Responder 37 | 1 | ||
| Anonymous Responder 38 | |||
| Anonymous Responder 39 | 1 | 1 | |
| Anonymous Responder 40 | |||
| Anonymous Responder 41 | 1 | ||
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| XML parser | 9 |
| RDF parser | 4 |
| HTML parser | 11 |
| HTTP | 27 |
| FTP | 9 |
| SSL | 14 |
| Don't know |
| Responder | XML parser | RDF parser | HTML parser | HTTP | FTP | SSL | Don't know | Comments |
|---|---|---|---|---|---|---|---|---|
| Anonymous Responder 1 | 1 | 1 | ||||||
| Anonymous Responder 2 | 1 | |||||||
| Anonymous Responder 3 | 1 | 1 | ||||||
| Anonymous Responder 4 | ||||||||
| Anonymous Responder 5 | 1 | |||||||
| Anonymous Responder 6 | 1 | 1 | 1 | |||||
| Anonymous Responder 7 | 1 | 1 | ||||||
| Anonymous Responder 8 | 1 | 1 | ||||||
| Anonymous Responder 9 | 1 | 1 | ||||||
| Anonymous Responder 10 | 1 | 1 | ||||||
| Anonymous Responder 11 | ||||||||
| Anonymous Responder 12 | ||||||||
| Anonymous Responder 13 | 1 | |||||||
| Anonymous Responder 14 | ||||||||
| Anonymous Responder 15 | 1 | 1 | 1 | 1 | 1 | 1 | Usually not all at once. | |
| Anonymous Responder 16 | ||||||||
| Anonymous Responder 17 | 1 | |||||||
| Anonymous Responder 18 | 1 | 1 | ||||||
| Anonymous Responder 19 | 1 | 1 | specifically for XML-RPC | |||||
| Anonymous Responder 20 | 1 | 1 | 1 | |||||
| Anonymous Responder 21 | 1 | 1 | 1 | |||||
| Anonymous Responder 22 | 1 | 1 | 1 | |||||
| Anonymous Responder 23 | 1 | 1 | ||||||
| Anonymous Responder 24 | 1 | Used as a spider | ||||||
| Anonymous Responder 25 | 1 | 1 | 1 | 1 | ||||
| Anonymous Responder 26 | 1 | 1 | 1 | 1 | ||||
| Anonymous Responder 27 | 1 | 1 | ||||||
| Anonymous Responder 28 | ||||||||
| Anonymous Responder 29 | 1 | 1 | 1 | 1 | ||||
| Anonymous Responder 30 | 1 | 1 | ||||||
| Anonymous Responder 31 | 1 | 1 | ||||||
| Anonymous Responder 32 | ||||||||
| Anonymous Responder 33 | 1 | 1 | 1 | 1 | 1 | |||
| Anonymous Responder 34 | 1 | 1 | 1 | |||||
| Anonymous Responder 35 | ||||||||
| Anonymous Responder 36 | ||||||||
| Anonymous Responder 37 | 1 | 1 | ||||||
| Anonymous Responder 38 | ||||||||
| Anonymous Responder 39 | We do not use libwww | |||||||
| Anonymous Responder 40 | ||||||||
| Anonymous Responder 41 | 1 | 1 | 1 | 1 | 1 | |||
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| I compile libwww myself | 21 |
| I use a pre-compiled 3rd party package (e.g. a .deb or .rpm package) | 11 |
| Responder | I compile libwww myself | I use a pre-compiled 3rd party package (e.g. a .deb or .rpm package) | Comments |
|---|---|---|---|
| Anonymous Responder 1 | 1 | ||
| Anonymous Responder 2 | 1 | ||
| Anonymous Responder 3 | 1 | ||
| Anonymous Responder 4 | 1 | ||
| Anonymous Responder 5 | 1 | ||
| Anonymous Responder 6 | i use Perl LWP | ||
| Anonymous Responder 7 | 1 | ||
| Anonymous Responder 8 | 1 | ||
| Anonymous Responder 9 | 1 | ||
| Anonymous Responder 10 | 1 | 1 | |
| Anonymous Responder 11 | |||
| Anonymous Responder 12 | |||
| Anonymous Responder 13 | 1 | ||
| Anonymous Responder 14 | |||
| Anonymous Responder 15 | 1 | 1 | Usually from CVS when in a research or the tar.gz in development mode. Packages are used to install on production systems. |
| Anonymous Responder 16 | |||
| Anonymous Responder 17 | 1 | ||
| Anonymous Responder 18 | |||
| Anonymous Responder 19 | 1 | deb package | |
| Anonymous Responder 20 | 1 | ||
| Anonymous Responder 21 | 1 | ||
| Anonymous Responder 22 | 1 | ||
| Anonymous Responder 23 | 1 | ||
| Anonymous Responder 24 | 1 | ||
| Anonymous Responder 25 | 1 | ||
| Anonymous Responder 26 | 1 | I use Gentoo, which automates compilation: $ emerge --search libwww Searching... [ Results for search key : libwww ] [ Applications found : 3 ] [...] * net-libs/libwww Latest version available: 5.4.0-r1 Latest version installed: 5.4.0-r1 Size of downloaded files: 1,102 kB Homepage: http://www.w3.org/Library/ Description: A general-purpose client side WEB API | |
| Anonymous Responder 27 | 1 | ||
| Anonymous Responder 28 | |||
| Anonymous Responder 29 | 1 | 1 | |
| Anonymous Responder 30 | 1 | ||
| Anonymous Responder 31 | 1 | ||
| Anonymous Responder 32 | |||
| Anonymous Responder 33 | 1 | 1 | debian's |
| Anonymous Responder 34 | 1 | ||
| Anonymous Responder 35 | |||
| Anonymous Responder 36 | |||
| Anonymous Responder 37 | 1 | ||
| Anonymous Responder 38 | |||
| Anonymous Responder 39 | |||
| Anonymous Responder 40 | |||
| Anonymous Responder 41 | 1 | ||
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| Yes | 14 |
| I was not aware of them | 4 |
| No, not required | 16 |
| Responder | 1.8 Do you use any of the applications that are part of libwww? |
|---|---|
| Anonymous Responder 1 | Yes |
| Anonymous Responder 2 | No, not required |
| Anonymous Responder 3 | No, not required |
| Anonymous Responder 4 | Yes |
| Anonymous Responder 5 | No, not required |
| Anonymous Responder 6 | Yes |
| Anonymous Responder 7 | No, not required |
| Anonymous Responder 8 | No, not required |
| Anonymous Responder 9 | Yes |
| Anonymous Responder 10 | No, not required |
| Anonymous Responder 11 | I was not aware of them |
| Anonymous Responder 12 | |
| Anonymous Responder 13 | Yes |
| Anonymous Responder 14 | |
| Anonymous Responder 15 | Yes |
| Anonymous Responder 16 | |
| Anonymous Responder 17 | Yes |
| Anonymous Responder 18 | Yes |
| Anonymous Responder 19 | Yes |
| Anonymous Responder 20 | No, not required |
| Anonymous Responder 21 | No, not required |
| Anonymous Responder 22 | Yes |
| Anonymous Responder 23 | No, not required |
| Anonymous Responder 24 | Yes |
| Anonymous Responder 25 | No, not required |
| Anonymous Responder 26 | Yes |
| Anonymous Responder 27 | No, not required |
| Anonymous Responder 28 | |
| Anonymous Responder 29 | Yes |
| Anonymous Responder 30 | I was not aware of them |
| Anonymous Responder 31 | No, not required |
| Anonymous Responder 32 | I was not aware of them |
| Anonymous Responder 33 | No, not required |
| Anonymous Responder 34 | No, not required |
| Anonymous Responder 35 | I was not aware of them |
| Anonymous Responder 36 | |
| Anonymous Responder 37 | No, not required |
| Anonymous Responder 38 | |
| Anonymous Responder 39 | No, not required |
| Anonymous Responder 40 | |
| Anonymous Responder 41 | Yes |
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| Examples | 9 |
| Robot | 6 |
| LineMode browser | 5 |
| Command line browser | 7 |
| WinCommander | 1 |
| Responder | Examples | Robot | LineMode browser | Command line browser | WinCommander | Comments |
|---|---|---|---|---|---|---|
| Anonymous Responder 1 | 1 | 1 | ||||
| Anonymous Responder 2 | ||||||
| Anonymous Responder 3 | ||||||
| Anonymous Responder 4 | 1 | 1 | ||||
| Anonymous Responder 5 | ||||||
| Anonymous Responder 6 | 1 | |||||
| Anonymous Responder 7 | ||||||
| Anonymous Responder 8 | ||||||
| Anonymous Responder 9 | 1 | |||||
| Anonymous Responder 10 | ||||||
| Anonymous Responder 11 | ||||||
| Anonymous Responder 12 | ||||||
| Anonymous Responder 13 | 1 | |||||
| Anonymous Responder 14 | ||||||
| Anonymous Responder 15 | 1 | 1 | 1 | 1 | ||
| Anonymous Responder 16 | ||||||
| Anonymous Responder 17 | 1 | 1 | ||||
| Anonymous Responder 18 | 1 | 1 | ||||
| Anonymous Responder 19 | 1 | |||||
| Anonymous Responder 20 | ||||||
| Anonymous Responder 21 | ||||||
| Anonymous Responder 22 | 1 | 1 | 1 | 1 | ||
| Anonymous Responder 23 | ||||||
| Anonymous Responder 24 | 1 | |||||
| Anonymous Responder 25 | ||||||
| Anonymous Responder 26 | 1 | 1 | 1 | |||
| Anonymous Responder 27 | ||||||
| Anonymous Responder 28 | ||||||
| Anonymous Responder 29 | 1 | |||||
| Anonymous Responder 30 | ||||||
| Anonymous Responder 31 | ||||||
| Anonymous Responder 32 | ||||||
| Anonymous Responder 33 | ||||||
| Anonymous Responder 34 | 1 | I have used examples a lot.. | ||||
| Anonymous Responder 35 | ||||||
| Anonymous Responder 36 | ||||||
| Anonymous Responder 37 | ||||||
| Anonymous Responder 38 | ||||||
| Anonymous Responder 39 | ||||||
| Anonymous Responder 40 | ||||||
| Anonymous Responder 41 | 1 | 1 | ||||
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| yes | 8 |
| no | 23 |
| Responder | 1.10 Have you had to patch the libwww code to be able to use it? |
|---|---|
| Anonymous Responder 1 | no |
| Anonymous Responder 2 | no |
| Anonymous Responder 3 | no |
| Anonymous Responder 4 | no |
| Anonymous Responder 5 | no |
| Anonymous Responder 6 | no |
| Anonymous Responder 7 | no |
| Anonymous Responder 8 | yes |
| Anonymous Responder 9 | yes |
| Anonymous Responder 10 | yes |
| Anonymous Responder 11 | no |
| Anonymous Responder 12 | |
| Anonymous Responder 13 | no |
| Anonymous Responder 14 | |
| Anonymous Responder 15 | yes |
| Anonymous Responder 16 | |
| Anonymous Responder 17 | no |
| Anonymous Responder 18 | no |
| Anonymous Responder 19 | no |
| Anonymous Responder 20 | yes |
| Anonymous Responder 21 | yes |
| Anonymous Responder 22 | no |
| Anonymous Responder 23 | no |
| Anonymous Responder 24 | no |
| Anonymous Responder 25 | no |
| Anonymous Responder 26 | no |
| Anonymous Responder 27 | yes |
| Anonymous Responder 28 | |
| Anonymous Responder 29 | no |
| Anonymous Responder 30 | no |
| Anonymous Responder 31 | no |
| Anonymous Responder 32 | |
| Anonymous Responder 33 | no |
| Anonymous Responder 34 | no |
| Anonymous Responder 35 | |
| Anonymous Responder 36 | |
| Anonymous Responder 37 | yes |
| Anonymous Responder 38 | |
| Anonymous Responder 39 | |
| Anonymous Responder 40 | |
| Anonymous Responder 41 | no |
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| yes | 7 |
| no | 3 |
| Responder | 1.11 If you answered Yes to 1.10, have you made your libwww patches publicly available? | Comments |
|---|---|---|
| Anonymous Responder 1 | ||
| Anonymous Responder 2 | ||
| Anonymous Responder 3 | ||
| Anonymous Responder 4 | ||
| Anonymous Responder 5 | ||
| Anonymous Responder 6 | ||
| Anonymous Responder 7 | ||
| Anonymous Responder 8 | no | |
| Anonymous Responder 9 | yes | URL removed |
| Anonymous Responder 10 | yes | It'd be useful to have an official place somewhere to dump patches, so they don't get lost. Always searching the mailing list archives is time-consuming... |
| Anonymous Responder 11 | ||
| Anonymous Responder 12 | ||
| Anonymous Responder 13 | ||
| Anonymous Responder 14 | ||
| Anonymous Responder 15 | yes | URL removed URL removed |
| Anonymous Responder 16 | ||
| Anonymous Responder 17 | ||
| Anonymous Responder 18 | yes | |
| Anonymous Responder 19 | ||
| Anonymous Responder 20 | no | For the most part they are hooks into our system and not useful to the public, however there are some fixes that we would not mind releasing. |
| Anonymous Responder 21 | yes | |
| Anonymous Responder 22 | Not applicable | |
| Anonymous Responder 23 | ||
| Anonymous Responder 24 | ||
| Anonymous Responder 25 | ||
| Anonymous Responder 26 | ||
| Anonymous Responder 27 | yes | Bugfix for pipelined posts |
| Anonymous Responder 28 | ||
| Anonymous Responder 29 | no | |
| Anonymous Responder 30 | ||
| Anonymous Responder 31 | ||
| Anonymous Responder 32 | ||
| Anonymous Responder 33 | ||
| Anonymous Responder 34 | ||
| Anonymous Responder 35 | ||
| Anonymous Responder 36 | ||
| Anonymous Responder 37 | yes | they are committed to CVS, but currently on a branch |
| Anonymous Responder 38 | ||
| Anonymous Responder 39 | ||
| Anonymous Responder 40 | ||
| Anonymous Responder 41 | ||
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| useful to write sample code | 15 |
| useful for learning how to program a WWW application | 20 |
| useful for writing production code | 22 |
| was not very useful | 1 |
| Responder | useful to write sample code | useful for learning how to program a WWW application | useful for writing production code | was not very useful | Comments |
|---|---|---|---|---|---|
| Anonymous Responder 1 | 1 | ||||
| Anonymous Responder 2 | 1 | Because libwww is modular, we were able to make use of it. For example, we wrote our own socket transport and file transport modules. Other similar open source libraries are not modular enough to be able to replace the parts that need to be replaced in a product environment. | |||
| Anonymous Responder 3 | 1 | ||||
| Anonymous Responder 4 | 1 | 1 | 1 | ||
| Anonymous Responder 5 | 1 | 1 | |||
| Anonymous Responder 6 | 1 | 1 | 1 | ||
| Anonymous Responder 7 | 1 | ||||
| Anonymous Responder 8 | 1 | ||||
| Anonymous Responder 9 | 1 | 1 | 1 | ||
| Anonymous Responder 10 | 1 | It's too complex just for sample code or learning how to program WWW apps. | |||
| Anonymous Responder 11 | |||||
| Anonymous Responder 12 | |||||
| Anonymous Responder 13 | 1 | ||||
| Anonymous Responder 14 | 1 | ||||
| Anonymous Responder 15 | 1 | 1 | |||
| Anonymous Responder 16 | |||||
| Anonymous Responder 17 | 1 | 1 | 1 | libwww was extremely useful as a means of supporting HTTP standards. | |
| Anonymous Responder 18 | 1 | 1 | It did seem a bit too ornamented, with too many hooks to be a solid demonstration of what was *needed*, and therefore too much footprint to use directly. | ||
| Anonymous Responder 19 | 1 | 1 | |||
| Anonymous Responder 20 | 1 | ||||
| Anonymous Responder 21 | 1 | 1 | 1 | ||
| Anonymous Responder 22 | 1 | ||||
| Anonymous Responder 23 | 1 | 1 | |||
| Anonymous Responder 24 | 1 | 1 | |||
| Anonymous Responder 25 | 1 | 1 | 1 | ||
| Anonymous Responder 26 | 1 | 1 | |||
| Anonymous Responder 27 | 1 | ||||
| Anonymous Responder 28 | |||||
| Anonymous Responder 29 | 1 | 1 | 1 | ||
| Anonymous Responder 30 | 1 | 1 | 1 | ||
| Anonymous Responder 31 | 1 | ||||
| Anonymous Responder 32 | 1 | ||||
| Anonymous Responder 33 | 1 | ||||
| Anonymous Responder 34 | 1 | 1 | 1 | ||
| Anonymous Responder 35 | |||||
| Anonymous Responder 36 | |||||
| Anonymous Responder 37 | |||||
| Anonymous Responder 38 | |||||
| Anonymous Responder 39 | |||||
| Anonymous Responder 40 | |||||
| Anonymous Responder 41 | 1 | 1 | 1 | ||
| Anonymous Responder 42 |
| Responder | Comments |
|---|---|
| Anonymous Responder 1 | |
| Anonymous Responder 2 | |
| Anonymous Responder 3 | |
| Anonymous Responder 4 | |
| Anonymous Responder 5 | The learning curve of the library is (too) steep. |
| Anonymous Responder 6 | |
| Anonymous Responder 7 | I do hope libwww can be maintained continously since I don't want to switch to use other open souces. |
| Anonymous Responder 8 | Great project to use as a base, but not in and of itself ready for prime time. |
| Anonymous Responder 9 | |
| Anonymous Responder 10 | libwww is the only library I know of which meets my demands: - Free - HTTP/1.1 support (both pipelining and ranges) - multiple simultaneous connections - portable to at least Windows and Unix The Mozilla code alone comes close to this but is no lib, and difficult to rip out. |
| Anonymous Responder 11 | |
| Anonymous Responder 12 | |
| Anonymous Responder 13 | |
| Anonymous Responder 14 | I plan on using libwww in the future, but being an insanely active high school student, have not had the right opportunity or the time to learn it yet. |
| Anonymous Responder 15 | We could move it to SourceForge ? |
| Anonymous Responder 16 | |
| Anonymous Responder 17 | My experience with libwww started very early in it's lifetime. I have continued to use tools built on libwww as a reference, to check standards compliance. Some sort of "reference implementation" of W3C standards is extremely useful. I still believe that support for HTTP standards in commercial software is poor, particularly with respect to content negotiation. |
| Anonymous Responder 18 | |
| Anonymous Responder 19 | |
| Anonymous Responder 20 | |
| Anonymous Responder 21 | libwww was instrumental in the development of Amaya |
| Anonymous Responder 22 | |
| Anonymous Responder 23 | |
| Anonymous Responder 24 | Thanks |
| Anonymous Responder 25 | |
| Anonymous Responder 26 | |
| Anonymous Responder 27 | |
| Anonymous Responder 28 | |
| Anonymous Responder 29 | |
| Anonymous Responder 30 | |
| Anonymous Responder 31 | |
| Anonymous Responder 32 | |
| Anonymous Responder 33 | |
| Anonymous Responder 34 | |
| Anonymous Responder 35 | |
| Anonymous Responder 36 | |
| Anonymous Responder 37 | |
| Anonymous Responder 38 | |
| Anonymous Responder 39 | |
| Anonymous Responder 40 | |
| Anonymous Responder 41 | |
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| yes | 40 |
| no | 1 |
| Responder | 2.1.1 Do you think it's worth it to have a WWW library? | Comments |
|---|---|---|
| Anonymous Responder 1 | yes | |
| Anonymous Responder 2 | yes | |
| Anonymous Responder 3 | yes | |
| Anonymous Responder 4 | yes | |
| Anonymous Responder 5 | yes | |
| Anonymous Responder 6 | yes | |
| Anonymous Responder 7 | yes | |
| Anonymous Responder 8 | yes | Absolutely, we would be interested in participating in a rewrite, certainly of the core http/html pieces. |
| Anonymous Responder 9 | yes | |
| Anonymous Responder 10 | yes | |
| Anonymous Responder 11 | yes | At the very least, as a test bed and for validation... |
| Anonymous Responder 12 | yes | |
| Anonymous Responder 13 | yes | |
| Anonymous Responder 14 | yes | |
| Anonymous Responder 15 | yes | |
| Anonymous Responder 16 | yes | |
| Anonymous Responder 17 | yes | As noted above, I believe some open-source "reference implementation" of core W3C standards is useful. Having this available in the "least common denominator" C language is useful for targets where other language support is less advanced, but it might be useful to utilize a subset of C++ and some other open-source projects, like Boost, in future libwww developments. |
| Anonymous Responder 18 | yes | |
| Anonymous Responder 19 | yes | |
| Anonymous Responder 20 | yes | |
| Anonymous Responder 21 | yes | |
| Anonymous Responder 22 | yes | |
| Anonymous Responder 23 | yes | |
| Anonymous Responder 24 | yes | |
| Anonymous Responder 25 | yes | |
| Anonymous Responder 26 | yes | |
| Anonymous Responder 27 | yes | |
| Anonymous Responder 28 | yes | |
| Anonymous Responder 29 | yes | |
| Anonymous Responder 30 | yes | |
| Anonymous Responder 31 | yes | |
| Anonymous Responder 32 | yes | |
| Anonymous Responder 33 | yes | |
| Anonymous Responder 34 | yes | |
| Anonymous Responder 35 | no | |
| Anonymous Responder 36 | yes | |
| Anonymous Responder 37 | yes | |
| Anonymous Responder 38 | yes | |
| Anonymous Responder 39 | yes | |
| Anonymous Responder 40 | This is what is called a 'loaded question'. Of course it's worth having a library like this, but it's *more worth* doing other things with limit resources. | |
| Anonymous Responder 41 | yes | |
| Anonymous Responder 42 | yes |
| Choice | All responders |
|---|---|
| Results | |
| Yes, libwww is a worthwhile project | 34 |
| No, libwww has lived beyond its time and should be stopped and let other projects follow its lead | 5 |
| Responder | 2.1.2 Should this WWW library be libwww? | |
|---|---|---|
| Anonymous Responder 1 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 2 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 3 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 4 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 5 | No, libwww has lived beyond its time and should be stopped and let other projects follow its lead | |
| Anonymous Responder 6 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 7 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 8 | Yes, libwww is a worthwhile project | There are alternatives out there but only libwww gives you a public option at doing server side work and having access to at least working reference library. |
| Anonymous Responder 9 | No, libwww has lived beyond its time and should be stopped and let other projects follow its lead | |
| Anonymous Responder 10 | Yes, libwww is a worthwhile project | Yes and no... I have to admit that the bitrot is severe in some places, and that I'd switch to something else any day *if there were an alternative*. |
| Anonymous Responder 11 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 12 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 13 | No, libwww has lived beyond its time and should be stopped and let other projects follow its lead | |
| Anonymous Responder 14 | Yes, libwww is a worthwhile project | I'm not really too sure about this, but I've from what I've read about libwww, it will be useful to me in the future. |
| Anonymous Responder 15 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 16 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 17 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 18 | Yes, libwww is a worthwhile project | There should be a reference library available at www.w3c.org at no cost. (Ideally, without license restrictions, but no cost is the crucial point for learning.) Simpler would be better. |
| Anonymous Responder 19 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 20 | Yes, libwww is a worthwhile project | At this point I am not aware of another library that would function in our application as well as libwww does, and clearly any such change would require a large change. |
| Anonymous Responder 21 | Yes, libwww is a worthwhile project | I am not aware of any other open source project fully implementing HTTP 1.1 |
| Anonymous Responder 22 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 23 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 24 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 25 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 26 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 27 | I'm not sure about it. I like libwww because it is running in our application quite fine now. Nevertheless I feel that the (often undocumented) internal structure of libwww makes it hard to integrate new features. | |
| Anonymous Responder 28 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 29 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 30 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 31 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 32 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 33 | Yes, libwww is a worthwhile project | I'm not sure I should say yes here. I'd like to see libwww integrated to glib/gnet library. I mean not just like glibwww, but make libwww glib'nized. |
| Anonymous Responder 34 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 35 | ||
| Anonymous Responder 36 | No, libwww has lived beyond its time and should be stopped and let other projects follow its lead | |
| Anonymous Responder 37 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 38 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 39 | Yes, libwww is a worthwhile project | For developers or organizations that wish to have a testbed, this is a useful tool |
| Anonymous Responder 40 | No, libwww has lived beyond its time and should be stopped and let other projects follow its lead | |
| Anonymous Responder 41 | Yes, libwww is a worthwhile project | |
| Anonymous Responder 42 | Can't determine. |
| Choice | All responders |
|---|---|
| Results | |
| yes | 14 |
| no | 24 |
| Responder | 2.2.1 Are you interested in joining the core team of such a project (enhancing, streamlining, rewriting libwww) | Comments |
|---|---|---|
| Anonymous Responder 1 | no | |
| Anonymous Responder 2 | no | I would be willing to contribute, but do not feel I have the time to be a "core team" member. |
| Anonymous Responder 3 | no | The RDF Parser is adequate enough for our needs |
| Anonymous Responder 4 | ||
| Anonymous Responder 5 | no | |
| Anonymous Responder 6 | no | |
| Anonymous Responder 7 | no | The main reason is because I am pretty new in libwww society. but I am certainly glad to help people and share what I know if I can. |
| Anonymous Responder 8 | yes | Absolutely, if w3c does not do it, we might be interested in working with another public effort at a rewrite. |
| Anonymous Responder 9 | ||
| Anonymous Responder 10 | yes | As usual, my spare time is very limited though :-/ |
| Anonymous Responder 11 | no | |
| Anonymous Responder 12 | no | |
| Anonymous Responder 13 | no | |
| Anonymous Responder 14 | no | |
| Anonymous Responder 15 | yes | URL removed |
| Anonymous Responder 16 | yes | |
| Anonymous Responder 17 | yes | Possibly, if W3C was willing to provide enough support to guide the feature list. |
| Anonymous Responder 18 | no | I would consider helping with a minimal reimplementation. Enhancements would only make it grow still larger and more arcane - and therefore less useful. |
| Anonymous Responder 19 | no | |
| Anonymous Responder 20 | yes | I would be happy to contribute as much as my skills and time allow. |
| Anonymous Responder 21 | no | No, for lack of resource. |
| Anonymous Responder 22 | yes | But I am not technically savvy enough. Could help with documentation, translations, and so on, though... |
| Anonymous Responder 23 | yes | In principle yes. But I probably do not know enough to do so. |
| Anonymous Responder 24 | no | Don't have the skill set to make a useful contribution. |
| Anonymous Responder 25 | no | |
| Anonymous Responder 26 | no | |
| Anonymous Responder 27 | no | |
| Anonymous Responder 28 | no | |
| Anonymous Responder 29 | yes | |
| Anonymous Responder 30 | no | |
| Anonymous Responder 31 | yes | |
| Anonymous Responder 32 | no | Currently no resources to do so. |
| Anonymous Responder 33 | yes | |
| Anonymous Responder 34 | yes | |
| Anonymous Responder 35 | ||
| Anonymous Responder 36 | yes | |
| Anonymous Responder 37 | no | |
| Anonymous Responder 38 | no | |
| Anonymous Responder 39 | no | |
| Anonymous Responder 40 | ||
| Anonymous Responder 41 | yes | |
| Anonymous Responder 42 | no |
| Choice | All responders |
|---|---|
| Results | |
| yes | 11 |
| no | 27 |
| Responder | 2.2.2 Would you feel more motivated to contribute to libwww if it were hosted outside of W3C? | |
|---|---|---|
| Anonymous Responder 1 | no | |
| Anonymous Responder 2 | no | |
| Anonymous Responder 3 | no | |
| Anonymous Responder 4 | no | |
| Anonymous Responder 5 | ||
| Anonymous Responder 6 | yes | |
| Anonymous Responder 7 | no | I can't see the difference |
| Anonymous Responder 8 | no | I'm motivated either way. |
| Anonymous Responder 9 | ||
| Anonymous Responder 10 | no | |
| Anonymous Responder 11 | no | |
| Anonymous Responder 12 | yes | |
| Anonymous Responder 13 | no | |
| Anonymous Responder 14 | yes | |
| Anonymous Responder 15 | yes | |
| Anonymous Responder 16 | yes | |
| Anonymous Responder 17 | no | I believe maintaining the value of libwww as a "reference implementation" requires some commitment by W3C to remain involved in an advisary role. |
| Anonymous Responder 18 | no | I would trust it less. |
| Anonymous Responder 19 | no | |
| Anonymous Responder 20 | no | |
| Anonymous Responder 21 | no | W3C is certainly the right home for such a project. |
| Anonymous Responder 22 | no | |
| Anonymous Responder 23 | no | |
| Anonymous Responder 24 | no | |
| Anonymous Responder 25 | no | |
| Anonymous Responder 26 | no | |
| Anonymous Responder 27 | no | |
| Anonymous Responder 28 | no | |
| Anonymous Responder 29 | no | |
| Anonymous Responder 30 | no | |
| Anonymous Responder 31 | yes | |
| Anonymous Responder 32 | no | That would make no difference to us. |
| Anonymous Responder 33 | yes | |
| Anonymous Responder 34 | yes | |
| Anonymous Responder 35 | ||
| Anonymous Responder 36 | yes | |
| Anonymous Responder 37 | yes | |
| Anonymous Responder 38 | no | |
| Anonymous Responder 39 | no | |
| Anonymous Responder 40 | ||
| Anonymous Responder 41 | yes | |
| Anonymous Responder 42 | no |
| Choice | All responders |
|---|---|
| Results | |
| SourceForge | 23 |
| I'm willing to host it myself | 1 |
| Other (please explain in the comments) | 5 |
| Responder | SourceForge | I'm willing to host it myself | Other (please explain in the comments) | Comments |
|---|---|---|---|---|
| Anonymous Responder 1 | 1 | |||
| Anonymous Responder 2 | ||||
| Anonymous Responder 3 | ||||
| Anonymous Responder 4 | ||||
| Anonymous Responder 5 | ||||
| Anonymous Responder 6 | 1 | |||
| Anonymous Responder 7 | ||||
| Anonymous Responder 8 | 1 | I could live with it hosted either at w3c or at sourceforge | ||
| Anonymous Responder 9 | ||||
| Anonymous Responder 10 | 1 | |||
| Anonymous Responder 11 | 1 | |||
| Anonymous Responder 12 | 1 | |||
| Anonymous Responder 13 | 1 | |||
| Anonymous Responder 14 | 1 | |||
| Anonymous Responder 15 | 1 | |||
| Anonymous Responder 16 | 1 | |||
| Anonymous Responder 17 | 1 | I have no strong opinions about where libwww should be hosted, but why couldn't W3C host it? | ||
| Anonymous Responder 18 | 1 | |||
| Anonymous Responder 19 | 1 | |||
| Anonymous Responder 20 | ||||
| Anonymous Responder 21 | ||||
| Anonymous Responder 22 | ||||
| Anonymous Responder 23 | 1 | |||
| Anonymous Responder 24 | 1 | |||
| Anonymous Responder 25 | 1 | |||
| Anonymous Responder 26 | 1 | 1 | SourceForge is a good fallback, but they are not ideal. During 2003, their servers have been overloaded, causing unavailability and slow response times. Their user interface (e.g. for bug trackers & mailing list archives) is also often a bit of a pain. | |
| Anonymous Responder 27 | ||||
| Anonymous Responder 28 | 1 | |||
| Anonymous Responder 29 | 1 | 1 | It should be hosted by W3C | |
| Anonymous Responder 30 | 1 | |||
| Anonymous Responder 31 | 1 | |||
| Anonymous Responder 32 | ||||
| Anonymous Responder 33 | 1 | gnome or glib/gnet | ||
| Anonymous Responder 34 | 1 | |||
| Anonymous Responder 35 | ||||
| Anonymous Responder 36 | 1 | |||
| Anonymous Responder 37 | 1 | hosting it at W3C would still be best, I guess | ||
| Anonymous Responder 38 | 1 | |||
| Anonymous Responder 39 | ||||
| Anonymous Responder 40 | ||||
| Anonymous Responder 41 | 1 | |||
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| yes | 9 |
| no | 25 |
| Responder | 2.2.4 Would you be interested in helping migrate the libwww project elsewhere? | |
|---|---|---|
| Anonymous Responder 1 | no | |
| Anonymous Responder 2 | no | |
| Anonymous Responder 3 | no | |
| Anonymous Responder 4 | ||
| Anonymous Responder 5 | ||
| Anonymous Responder 6 | yes | |
| Anonymous Responder 7 | no | |
| Anonymous Responder 8 | yes | Again, more than willing, but my lack of experience in public projects would be a hinderance. On the other hand I could crank out a lot of good code on a new library if needed. I just am not familiar with the check in/out process of the public efforts. |
| Anonymous Responder 9 | ||
| Anonymous Responder 10 | no | |
| Anonymous Responder 11 | no | |
| Anonymous Responder 12 | no | |
| Anonymous Responder 13 | no | |
| Anonymous Responder 14 | no | Don't have time to help with a simple task like "migration" (as I understand it would be). All that's required is to set up the project and then copy the files over, right? |
| Anonymous Responder 15 | yes | |
| Anonymous Responder 16 | yes | |
| Anonymous Responder 17 | I don't know what is involved in the migration. Has anyone evaluated this? | |
| Anonymous Responder 18 | no | |
| Anonymous Responder 19 | yes | |
| Anonymous Responder 20 | no | |
| Anonymous Responder 21 | no | |
| Anonymous Responder 22 | ||
| Anonymous Responder 23 | no | |
| Anonymous Responder 24 | yes | If I can help - I'm happy to. |
| Anonymous Responder 25 | no | |
| Anonymous Responder 26 | ||
| Anonymous Responder 27 | no | |
| Anonymous Responder 28 | no | |
| Anonymous Responder 29 | yes | Only if it is tied to my work |
| Anonymous Responder 30 | no | |
| Anonymous Responder 31 | yes | |
| Anonymous Responder 32 | no | |
| Anonymous Responder 33 | yes | |
| Anonymous Responder 34 | no | |
| Anonymous Responder 35 | ||
| Anonymous Responder 36 | no | |
| Anonymous Responder 37 | no | |
| Anonymous Responder 38 | no | |
| Anonymous Responder 39 | no | |
| Anonymous Responder 40 | ||
| Anonymous Responder 41 | no | |
| Anonymous Responder 42 | no |
| Responder | Comments |
|---|---|
| Anonymous Responder 1 | |
| Anonymous Responder 2 | |
| Anonymous Responder 3 | |
| Anonymous Responder 4 | |
| Anonymous Responder 5 | |
| Anonymous Responder 6 | |
| Anonymous Responder 7 | |
| Anonymous Responder 8 | I absolutely believe its worth the effort to rewrite, I view it as more a management problem than anything else. To me a potential process would be to: 1. Do it in C++ 2. Use STL to replace a lot of the low level stuff 3. Have a couple meetings of cogniscenti to figure out what stuff in the libwww architecture works, and what does not. 4. Do a redesign that lead to release of the library in distinct usable components |
| Anonymous Responder 9 | |
| Anonymous Responder 10 | |
| Anonymous Responder 11 | |
| Anonymous Responder 12 | |
| Anonymous Responder 13 | |
| Anonymous Responder 14 | |
| Anonymous Responder 15 | There are many libraries implemented in many languages to exchange information using http and https. It is convenient to have access to a library of function that is both written to the specification and useable for production tools. |
| Anonymous Responder 16 | |
| Anonymous Responder 17 | |
| Anonymous Responder 18 | |
| Anonymous Responder 19 | I was evaluating this for use in a commercial product, when the end-of-life was announced. |
| Anonymous Responder 20 | One of the most important things to me that I would like to see in libwww is support for multiple simultaneous connections to a single host. |
| Anonymous Responder 21 | |
| Anonymous Responder 22 | |
| Anonymous Responder 23 | |
| Anonymous Responder 24 | |
| Anonymous Responder 25 | |
| Anonymous Responder 26 | |
| Anonymous Responder 27 | |
| Anonymous Responder 28 | |
| Anonymous Responder 29 | |
| Anonymous Responder 30 | |
| Anonymous Responder 31 | I am very interested in hosting libwww. I would like to use it to create open source Web services for deep Web sites. Essentially, I would like to use it to create open source APIs like the Google APIs for commercial and public deep Web pages (pages behind a FORM). My plan is to create tools, based on libwww's HTTP and HTML parsing capabilities, that would allow the open source community to turn any website into a Web service. I would maintain libwww, the tools added to it, and the APIs or Web services that the open source community creates. Of course, all of this code would be open source. I have used libwww's HTTP and HTML facilities and believe, with a little modification, that it can do the job. Please let me know if you would be interested in having me host libwww and/or working with me on turning Web pages into Web Services. REMOVED NAME AND ADDRESS FOR ANONYMIZING |
| Anonymous Responder 32 | |
| Anonymous Responder 33 | |
| Anonymous Responder 34 | |
| Anonymous Responder 35 | |
| Anonymous Responder 36 | |
| Anonymous Responder 37 | |
| Anonymous Responder 38 | |
| Anonymous Responder 39 | |
| Anonymous Responder 40 | |
| Anonymous Responder 41 | |
| Anonymous Responder 42 |
| Responder | Comments |
|---|---|
| Anonymous Responder 1 | |
| Anonymous Responder 2 | cURL (not modular enough to be able to replace socket usage or event loop) |
| Anonymous Responder 3 | |
| Anonymous Responder 4 | |
| Anonymous Responder 5 | LibCurl |
| Anonymous Responder 6 | |
| Anonymous Responder 7 | |
| Anonymous Responder 8 | I used to, I know there is a client side lib that is closes, think its called something like curl. |
| Anonymous Responder 9 | http://curl.haxx.se/ |
| Anonymous Responder 10 | Mozilla netlib: Very good HTTP/1.1 support, well-tested, portable; OTOH, big amount of code (and depends on other Moz libs), not easy to rip out AFAIK http://www.mozilla.org/projects/netlib/ libcurl: Easy, simple, clean, portable, ip6, enough for most people's needs; OTOH, no HTTP pipelining (just persistent connections) http://curl.haxx.se/libcurl/ Also see the excellent list at http://curl.haxx.se/libcurl/competitors.html and http://curl.haxx.se/docs/comparison-table.html |
| Anonymous Responder 11 | |
| Anonymous Responder 12 | |
| Anonymous Responder 13 | Mozilla |
| Anonymous Responder 14 | |
| Anonymous Responder 15 | |
| Anonymous Responder 16 | |
| Anonymous Responder 17 | |
| Anonymous Responder 18 | Several languages (including java and python) include web libraries. Several open source browsers (including Mozilla) exist. But they're not independent packages, they may be much too large, and there is a quality concern. (Is the python library correct, or just "close"?) |
| Anonymous Responder 19 | |
| Anonymous Responder 20 | |
| Anonymous Responder 21 | |
| Anonymous Responder 22 | |
| Anonymous Responder 23 | There is libwww-perl which is available from CPAN and works with the Perl network interface. However, this cannot be linked into C or any other form of executable code. |
| Anonymous Responder 24 | http://wanto.f2o.org/projects/NetSpider/ |
| Anonymous Responder 25 | I do not know any other. I never needed another. |
| Anonymous Responder 26 | http://curl.haxx.se/ http://pycurl.sourceforge.net |
| Anonymous Responder 27 | |
| Anonymous Responder 28 | |
| Anonymous Responder 29 | |
| Anonymous Responder 30 | |
| Anonymous Responder 31 | |
| Anonymous Responder 32 | |
| Anonymous Responder 33 | |
| Anonymous Responder 34 | Libcurl |
| Anonymous Responder 35 | |
| Anonymous Responder 36 | |
| Anonymous Responder 37 | |
| Anonymous Responder 38 | |
| Anonymous Responder 39 | |
| Anonymous Responder 40 | |
| Anonymous Responder 41 | |
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| HTTP/1.0 | 8 |
| HTTP/1.1 | 9 |
| Pipelining | 3 |
| Caching | |
| HTTP Persistent Connections (Keep-Alive) | 5 |
| HTTP PUT | 6 |
| WebDav | |
| Basic Authentication | 6 |
| Digest Authentication | 2 |
| HTTPS (SSL) | 6 |
| Conditional Requests (e.g., If-Modified-Since, If-Match, ...) | 1 |
| SOAP | 1 |
| Responder | HTTP/1.0 | HTTP/1.1 | Pipelining | Caching | HTTP Persistent Connections (Keep-Alive) | HTTP PUT | WebDav | Basic Authentication | Digest Authentication | HTTPS (SSL) | Conditional Requests (e.g., If-Modified-Since, If-Match, ...) | SOAP | Comments |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Anonymous Responder 1 | |||||||||||||
| Anonymous Responder 2 | |||||||||||||
| Anonymous Responder 3 | |||||||||||||
| Anonymous Responder 4 | |||||||||||||
| Anonymous Responder 5 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| Anonymous Responder 6 | |||||||||||||
| Anonymous Responder 7 | |||||||||||||
| Anonymous Responder 8 | 1 | 1 | 1 | 1 | 1 | 1 | We are running against a wide variety of web servers and with some tweaking libwww can be made to run against them all. We are also running it against some web services and again, with tweaking works great. | ||||||
| Anonymous Responder 9 | 1 | 1 | 1 | 1 | 1 | 1 | libcurl probably does more than the above but I've only tested it for my current requirements. | ||||||
| Anonymous Responder 10 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||
| Anonymous Responder 11 | |||||||||||||
| Anonymous Responder 12 | |||||||||||||
| Anonymous Responder 13 | 1 | 1 | |||||||||||
| Anonymous Responder 14 | |||||||||||||
| Anonymous Responder 15 | |||||||||||||
| Anonymous Responder 16 | |||||||||||||
| Anonymous Responder 17 | |||||||||||||
| Anonymous Responder 18 | 1 | 1 | 1 | 1 | 1 | 1 | I have indicated my best guess for the current python library. I expect more to be added - I may do it myself. But is it correct? Complete? | ||||||
| Anonymous Responder 19 | |||||||||||||
| Anonymous Responder 20 | |||||||||||||
| Anonymous Responder 21 | |||||||||||||
| Anonymous Responder 22 | |||||||||||||
| Anonymous Responder 23 | 1 | ||||||||||||
| Anonymous Responder 24 | 1 | Very basic spider | |||||||||||
| Anonymous Responder 25 | |||||||||||||
| Anonymous Responder 26 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||
| Anonymous Responder 27 | |||||||||||||
| Anonymous Responder 28 | |||||||||||||
| Anonymous Responder 29 | |||||||||||||
| Anonymous Responder 30 | |||||||||||||
| Anonymous Responder 31 | |||||||||||||
| Anonymous Responder 32 | |||||||||||||
| Anonymous Responder 33 | |||||||||||||
| Anonymous Responder 34 | 1 | 1 | 1 | ||||||||||
| Anonymous Responder 35 | |||||||||||||
| Anonymous Responder 36 | |||||||||||||
| Anonymous Responder 37 | |||||||||||||
| Anonymous Responder 38 | |||||||||||||
| Anonymous Responder 39 | |||||||||||||
| Anonymous Responder 40 | |||||||||||||
| Anonymous Responder 41 | |||||||||||||
| Anonymous Responder 42 |
| Choice | All responders |
|---|---|
| Results | |
| I'm a developer of the library | |
| I only use it for my applications | 12 |
| Responder | 2.3.3 What is your involvement with those libraries? | Comments |
|---|---|---|
| Anonymous Responder 1 | ||
| Anonymous Responder 2 | ||
| Anonymous Responder 3 | ||
| Anonymous Responder 4 | ||
| Anonymous Responder 5 | I only use it for my applications | |
| Anonymous Responder 6 | ||
| Anonymous Responder 7 | I only use it for my applications | |
| Anonymous Responder 8 | I only use it for my applications | I have made numerous changes to the core libwww source to make the above features work on various web servers. |
| Anonymous Responder 9 | I only use it for my applications | |
| Anonymous Responder 10 | I only use it for my applications | |
| Anonymous Responder 11 | ||
| Anonymous Responder 12 | ||
| Anonymous Responder 13 | I only use it for my applications | |
| Anonymous Responder 14 | ||
| Anonymous Responder 15 | ||
| Anonymous Responder 16 | ||
| Anonymous Responder 17 | ||
| Anonymous Responder 18 | I only use it for my applications | I have contributed minor patches, because the code was sufficiently small and clean that I could get a handle on what *should* happen where, and then find the problem. wwwlib didn't really have an easy entry point, and there weren't many files that I could follow without having several support files open at the same time. |
| Anonymous Responder 19 | ||
| Anonymous Responder 20 | ||
| Anonymous Responder 21 | ||
| Anonymous Responder 22 | ||
| Anonymous Responder 23 | I only use it for my applications | |
| Anonymous Responder 24 | I only use it for my applications | |
| Anonymous Responder 25 | ||
| Anonymous Responder 26 | I only use it for my applications | |
| Anonymous Responder 27 | ||
| Anonymous Responder 28 | ||
| Anonymous Responder 29 | I only use it for my applications | |
| Anonymous Responder 30 | ||
| Anonymous Responder 31 | ||
| Anonymous Responder 32 | ||
| Anonymous Responder 33 | ||
| Anonymous Responder 34 | I only use it for my applications | |
| Anonymous Responder 35 | ||
| Anonymous Responder 36 | ||
| Anonymous Responder 37 | ||
| Anonymous Responder 38 | ||
| Anonymous Responder 39 | ||
| Anonymous Responder 40 | ||
| Anonymous Responder 41 | ||
| Anonymous Responder 42 |
| Responder | Comments |
|---|---|
| Anonymous Responder 1 | |
| Anonymous Responder 2 | |
| Anonymous Responder 3 | |
| Anonymous Responder 4 | |
| Anonymous Responder 5 | Although not as complete as LibWWW, the learning curve of LibCURL is less steep. The library is actively maintained, and it's fast. For our use: sending and reveiving SOAP messages it's a nice library. |
| Anonymous Responder 6 | |
| Anonymous Responder 7 | |
| Anonymous Responder 8 | |
| Anonymous Responder 9 | |
| Anonymous Responder 10 | |
| Anonymous Responder 11 | |
| Anonymous Responder 12 | |
| Anonymous Responder 13 | |
| Anonymous Responder 14 | |
| Anonymous Responder 15 | |
| Anonymous Responder 16 | |
| Anonymous Responder 17 | |
| Anonymous Responder 18 | |
| Anonymous Responder 19 | |
| Anonymous Responder 20 | |
| Anonymous Responder 21 | |
| Anonymous Responder 22 | |
| Anonymous Responder 23 | |
| Anonymous Responder 24 | |
| Anonymous Responder 25 | |
| Anonymous Responder 26 | |
| Anonymous Responder 27 | |
| Anonymous Responder 28 | |
| Anonymous Responder 29 | |
| Anonymous Responder 30 | |
| Anonymous Responder 31 | |
| Anonymous Responder 32 | |
| Anonymous Responder 33 | |
| Anonymous Responder 34 | |
| Anonymous Responder 35 | |
| Anonymous Responder 36 | |
| Anonymous Responder 37 | |
| Anonymous Responder 38 | |
| Anonymous Responder 39 | |
| Anonymous Responder 40 | |
| Anonymous Responder 41 | |
| Anonymous Responder 42 |
Full statement of question.
| Responder | Comments |
|---|---|
| Anonymous Responder 1 | |
| Anonymous Responder 2 | |
| Anonymous Responder 3 | |
| Anonymous Responder 4 | |
| Anonymous Responder 5 | |
| Anonymous Responder 6 | |
| Anonymous Responder 7 | |
| Anonymous Responder 8 | Lets do it! |
| Anonymous Responder 9 | I started looking at libwww in July 2003. I found libwww quite powerful. Some truly great work went into it! At first I found the architecture a bit difficult to understand. libcurl is much easier to get started with. My main reason for abandoning Libwww in favour of libcurl was that it didn't seem as though there was much activity on it. The online CVS did not appear to be updated frequently anymore. I was a bit nervous about memory leaks and errors. Although most were benign I didn't feel comfortable about releasing commercial software with such problems. I tried to debug the code but gave up when the problem I tried to solve appeared to be in the design which I didn't understand well enoug |
| Anonymous Responder 10 | |
| Anonymous Responder 11 | |
| Anonymous Responder 12 | |
| Anonymous Responder 13 | |
| Anonymous Responder 14 | |
| Anonymous Responder 15 | |
| Anonymous Responder 16 | |
| Anonymous Responder 17 | |
| Anonymous Responder 18 | |
| Anonymous Responder 19 | I don't use it a huge amount, but I think it has enormous value as a reference implementation. Such libraries, when developed as part of other projects, seem to invariably become inextricably intertwined with the rest of such projects' code and/or susceptible to bloat. |
| Anonymous Responder 20 | |
| Anonymous Responder 21 | It is bad news that W3C is unable to continue its work on libwww. Even if no new developements are planned for HTTP, libwww is still a good support for the most recent features of HTTP, which are not widespread yet. Even a feature such as PUT is not reasonably supported in the latest versions of Apache. |
| Anonymous Responder 22 | |
| Anonymous Responder 23 | |
| Anonymous Responder 24 | |
| Anonymous Responder 25 | |
| Anonymous Responder 26 | |
| Anonymous Responder 27 | Perhaps there can be a way in the middle (which has been mostly done during the last months): Do only maintenance on the software but do not integrate new features. The general decision may free resources if not every feature request must be thought about individually. |
| Anonymous Responder 28 | |
| Anonymous Responder 29 | |
| Anonymous Responder 30 | |
| Anonymous Responder 31 | |
| Anonymous Responder 32 | |
| Anonymous Responder 33 | |
| Anonymous Responder 34 | I hate to see the work stop on this .... Great if we can move it to sourcefrge and get people incolved... |
| Anonymous Responder 35 | |
| Anonymous Responder 36 | |
| Anonymous Responder 37 | |
| Anonymous Responder 38 | |
| Anonymous Responder 39 | |
| Anonymous Responder 40 | |
| Anonymous Responder 41 | I like the library and want it to be supported in the future. |
| Anonymous Responder 42 |
Only available to W3C Team members