Closed daria-kopaliani closed 10 years ago
I'm not sure if absoluteString is a good idea. According to rfc
this url doesn't have an extension, so this behaviour is kind of expected. I think that parsing parameters as fallback can be considered.
I was hoping there was some way to manually specify which decoder you want rather than assuming it can always be derived from the URL. I'm working with a webservice right now that provides files with a URL like /track/:id/:format
i.e
http://my.site/track/1337/opus
I might pull request a proper fix later on if I can find the time and if there's any demand for such functionality. In my project at the moment I'm just monkeypatching in a custom ORGMSource
which tells the rest of the OrigamiEngine system that the URL has a certain path extension, but then proceeds to open a NSURLRequest without the extension...
Hi Tyrone, thanks for the suggestion. I actually like this idea with customisations for the plugin resolution process. What I'm thinking is instead of using ORGMPluginManager
singleton for the plugin resolution, I can allow users to provide custom plugin manager(or resolver) that will return classes according to user's expectations. Let me see what I can do.
For instance if
source
url looks like this "http://someurl?someparameters&1234.m4a",extension
will be nil and thereforedecoder
will also be nil. UsingabsoluteString
instead ofpath
will solve this issue.