Re: Re: Of saving a QTMovie created from a NSURL and the resulting disappointments
Re: Re: Of saving a QTMovie created from a NSURL and the resulting disappointments
- Subject: Re: Re: Of saving a QTMovie created from a NSURL and the resulting disappointments
- From: "Hari Seldon" <email@hidden>
- Date: Fri, 7 Jul 2006 15:13:20 -0500
Thanks for the tip; after some searching, I found a posting to a
WebKit mailing list that describes how to subclass the HTTP
NSURLProtocol.
http://lists.apple.com/archives/Webkitsdk-dev/2004/Feb/msg00088.html
Is this what you're describing? Any other ideas?
On 7/6/06, Michael Ash <email@hidden> wrote:
I can't answer the first part of the question, but I can give a try at
the second part.
Writing a custom NSURLProtocol isn't all that difficult. It would be
possible to write one that just wraps a standard HTTP handler (or a
fancier one that can wrap any sort of URL), and then saves the
incoming data to a file or to memory while simultaneously forwarding
the data to the requesting object. You could then give an URL with
your custom scheme to QTMovie and, assuming it does everything kosher,
it would then invoke your custom NSURLProtocol which lets you get at
the raw data.
Obviously this is suboptimal, but if you're seeing the same results as
you see by doing "Save as Source..." then there probably isn't a way
to make the obvious technique work.
Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden