"Erik Huelsmann" <ehuels@gmail.com> writes:
> Can you expand on what you think you're saying here? I don't get the
> solution you two are discussing:
>
> 1) I think Ben is talking about discovering server capabilities while
> you are talking about sending client capabilities to the server.
> 2) HTTP is stateless, meaning that stuff from a previous request
> should not 'stick'.
>
> These two things are what's confusing me. I hope you understand me
> enough to make me understand you :-)
Oh, I definitely understand you -- in fact, this statelessness was the
reason I didn't do things that way in the first place. (I'm pretty
sure Ben was talking about server discovery of client capabilities,
though: he just meant to send them in the headers of an initial
OPTIONS request).
Our worries seem unfounded: see r27647. It's true that HTTP can be
stateless. But in practice, our client opens one session and does
multiple requests/responses over it. I beleve note we were already
depending on this, too: see the assignment to repos->is_svn_client in
subversion/mod_dav_svn/repos.c, for example.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 7 17:51:00 2007