[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: confused about serf OPTIONS request

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: Tue, 23 Dec 2008 16:07:14 -0600

OK, so I'm now modifying the more general
svn_ra_serf__create_options_req() not only request an
activity-collection, but *also* always parse the server's capabilities
headers directly into the serf-session's capability hash. Then I can
make the whole exchange_capabilities() utility call the generic
OPTIONS request generator.

Once that's done, I can *also* make the general function notice the
new v2 protocol "stubs" and stash them in the serf session.

The end result is that serf's OPTIONS code will be unified, and all
OPTIONS requests always get the maximum amount of server information
into the session.

On Mon, Dec 22, 2008 at 12:27 PM, Lieven Govaerts <svnlgo_at_mobsol.be> wrote:
> Ben,
> Ben Collins-Sussman wrote:
>> When I look at serf's options.c file, it appears that it *always*
>> sends an OPTIONS request which includes "D:activity-collections-set"
>> in the body.
>> And yet when I set 'http-library = serf" in my ~/.subversion/servers
>> file, and then run "svn ls http://localhost/repos/test2", my wire
>> capture shows *no* body in the OPTIONS request.
> The only OPTIONS request sent with 'svn ls' is used for the capabilities
> check. This doesn't use the code in options.c, but the
> exchange_capabilities code in serf.c. The same method, but no body.
> hth,
> Lieven

Received on 2008-12-23 23:07:30 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.