Daniel Stenberg wrote:
> On Sun, 2 May 2010, Howard Chu wrote:
>> I'll need to study the libcurl code and think about this some more...
>
> Sure! Just ask if there's anything else I can help to clarify (or totally
> confuse you with!) ;-)
>
Here's a first cut at the code. Sorry I haven't added the configure checks for
it yet. Just figured I'd get it out there as a strawman at least. This patch
assumes that the modular I/O patch I posted has already been applied.

librtmp doesn't like non-blocking sockets; we normally just use a receive
timeout. So that's what I've done here; it would be rather painful to change
this behavior...

There is no mechanism for querying the byte length of a stream from the server
before retrieving it, so it seems I have no nice way to indicate the end of a
transfer. I tried to kludge it in rtmp_recv() but that had no effect, I just
eventually get a poll() error because the server has closed the socket.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html