On Wed, 2010-01-20 at 23:50 +0100, Daniel Stenberg wrote:
> On Mon, 18 Jan 2010, Chris Conroy wrote:
>
> > Here is an updated patch that pulls your changes in rtsp-3.patch and also
> > addresses the concerns about the RTPFUNCTION, the checking of return codes,
> > the bad expect100 merge, and CURLOPT_RTSPVERSION.
>
> Cool. I've edited it a bit more now, and I'm prepared to commit what I have in
> a short while and then we should be able to continue smoothen out the
> remaining quirks against CVS.

Great news!

As for unit tests, I probably spent far too long trying fighting the
test framework to no avail. A lot of it is pretty protocol-centric and
I'm not much of a perl hacker. At first I figured I could just crib from
the HTTP tests and tell it to use RTSP instead, but it turns out the
test backend doesn't quite work that way..

Unless I'm missing something, it seems like the SWS code will need to be
modified to support RTSP. However, perhaps the more general ping-pong
framework would suffice? I'd be fine with a really stupid back-end that
I simply feed with data defining the Request->Response flow of any given
test. If that already exists somewhere in the ping-pong stuff, please
let me know how to use it. The only relatively complicated thing would
be stuffing RTP data into the responses.

Let me know which approach you think is best.

P.S. While I'm on the subject. My autotools-fu is not that great, and in
trying to make some test cases I found that to add one to the project I
need to make distclean, buildconf, make curl, then make test. Is there
any way to just re-run the buildconf for the tests/ directory only?

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-01-21