[Dav-linuxfs] more on the 'source' resource.

[Anthony B. <an...@in...>]

Ok, I'm getting into this - for starters, current CVS is now able
to view the rendered methods. This is good. I'm trying to work out
the best way to handle the :source stuff. Now, as far as I can see,
it goes something like this:

  user runs "cat test_method"
     |
  kernel module does "attr - /path/to/test_method"
     |
  davfsd does "PROPFIND /path/to/test_method"
     | 
  sends result back to kernel module
     | 
  kernel module "open - /path/to/test_method"
     |
  davfsd does "GET /path/to/test_method"
     |
  sends data back to kernel module

Now, I'm wondering where the bit that says "oo, actually, I want the 
source" should go. It doesn't really make sense (to me) to have the 
kernel module knowing about this. For now, I'm going to make client_open 
do another PROPFIND for the source property to check if it's got one, 
and if so, use the destination of that, instead. I'm not even going 
to consider what should happen if the source link points to a different 
server... :-/

Anthony