Implementing svn_ra_list for ra_serf

[Stefan Fuhrmann <st...@apache.org>]

Hi there,

I was playing around with ra_serf to find out
what the Right Way to implement svn_ra_list
would be. But I can't decide which of the two
options would be the better one:

* Implement it similar get_list, i.e. based upon
   PROPFIND. That would require us adding the
   filter patterns as additional request headers.

* Invent a new custom report similar to get_log.
   Most of the DIRENT handling would then either
   be duplicated or get an alternative implementation.

So, which route should we take?

-- Stefan^2.

RE: Implementing svn_ra_list for ra_serf

[Bert Huijben <be...@qqmail.nl>]

> -----Original Message-----
> From: Stefan Fuhrmann [mailto:stefan2@apache.org]
> Sent: dinsdag 15 november 2016 12:46
> To: Subversion Development <de...@subversion.apache.org>
> Subject: Implementing svn_ra_list for ra_serf
> 
> Hi there,
> 
> I was playing around with ra_serf to find out
> what the Right Way to implement svn_ra_list
> would be. But I can't decide which of the two
> options would be the better one:
> 
> * Implement it similar get_list, i.e. based upon
>    PROPFIND. That would require us adding the
>    filter patterns as additional request headers.

If the PROPFIND request doesn't make the current server cache all results in ram, we could do optional server side filtering via the new header + always client side filtering here, to allow the new code to work against old servers...

	Bert