HTTP-DAV
view release on metacpan or search on metacpan
doc/html/TODO.html view on Meta::CPAN
<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>TODO</title>
<link rel="stylesheet" href="perldav.css" type="text/css" />
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>
<body>
<div id="content"><H1>TODO</H1></div><div id="content">
<h2 id="dave">dave</h2>
<pre><code>- globs on lock(),unlock(),steal(),options()?,move(),copy(),propfind(),proppatch() (and set/unset).
- rework ls to use globs.
- multistatus responses don't come through nicely.</code></pre>
<h2 id="HTTP::DAV">HTTP::DAV</h2>
<pre><code>- Rework the file transfer code to avoid slurping complete files in memory
and read through a fixed size buffer, to avoid memory hogs or crashes
when transferring huge files.
- LWP doesn't allow callback on upload, only download. This means
we can't do progress indicators on "PUT". How to do it? Could patch
LWP? Specialise LWP::UserAgent? Ugh.
- doco globs in DAV.pm
- fix get references
- _put calls propfind on every call throughout a recursive _put().
need to adjust this so that it does it only once, in put(). After
the first time, we should be able to KNOW whether it is a collection
or not instead of having to propfind to find out becasue in theory
WE were the ones who put the file there.
- finish "source" property in DAV::Resource.pm
- redo POD Resource.pm
- setup_if_headers need to get just Rsource's locks not all RL's locks.
- discovery still isn't resetting locks properly ????
- DAV.pm as_string needs working resource
- finish lock (bug against mod_dav somewhere)
- mod t/* for IIS 5 lock and proppatch deficiencies.
- how to we handle degradation for incomplete servers in test suite (IIS)?
- mod_dav has a very strange bug with lock-null resources.
The following combination of commands makes it weird out:
$ mkdir dir1
$ lock dir1
$ lock dir2 (this is a lock null)
$ move dir1 dir2
Now, the spec says that dir2 should now be the copy of dir1 and it should be locked.
However, mod_dav has an unlocked dir2. Even worse, if you delete dir2, there is
a shadowed lock-null resource called dir2 sitting behind the scenes. Bad.</code></pre>
<h2 id="Wishlist-functions">Wishlist functions</h2>
<pre><code>- testing against Zope
( run in 0.560 second using v1.01-cache-2.11-cpan-e1769b4cff6 )