| 1 |
|
| 2 |
To Do List for neon -*- text -*- |
| 3 |
=================== |
| 4 |
|
| 5 |
Please submit feature requests to <[email protected]> |
| 6 |
|
| 7 |
For one-point-oh |
| 8 |
---------------- |
| 9 |
|
| 10 |
Longer term |
| 11 |
----------- |
| 12 |
|
| 13 |
6. PUT with ranges... ne_put_range |
| 14 |
|
| 15 |
9. DeltaV support (http://www.webdav.org/deltav/). See also the |
| 16 |
subversion project (http://subversion.tigris.org/) who might build |
| 17 |
a versioning system over DAV. |
| 18 |
|
| 19 |
14. Improved request-header manipulation... some kind of indexed table |
| 20 |
(a la Apache, libghttp, so we're sure we don't add the same header |
| 21 |
to the request twice. Better control over adding Cache-Control |
| 22 |
headers would be good too. |
| 23 |
|
| 24 |
21. Storing multiple authentication "sessions" within an actual |
| 25 |
auth_session, so I can log into e.g. /foo/ and /bar/ (which are |
| 26 |
not in the same authentication domain) and switch between them |
| 27 |
without having to re-enter passwords all the time. |
| 28 |
|
| 29 |
46. Asynchronous request-dispatching? Makes integration into GUI loop |
| 30 |
easy... any other reasons? Must leave existing request_dispatch |
| 31 |
interface intact. |
| 32 |
|
| 33 |
50. opendir/readdir/closedir-esque interface for PROPFIND depth 1, |
| 34 |
a la EZDAV. (cadaver has it already) |
| 35 |
|