I have some legacy secure limelight content that I've made play with what I consider a hack and I was wondering if the OSMF group could weigh in on the right way to do this. Briefly, the limelight secure content URI format is different than the the typical FMS format -- there's an extra /s/ for secure. You can see the URI below. The issue is that FMSURL incorrectly parses the URI and both the appname and streamName are incorrect. As a workaround I wrote a dummy limelight plugin with custom buildConnectionAddress() and play() handlers to correct the paths, but this seems like the wrong approach. It seems like there should be a way to extend FMSURL to correctly parse the original URI, possibly have the plugin do the parsing, but I haven't found a way. What am I missing?
Stream name w/ authentication:
A bit of confusion here, the s/ should be a part of the stream name.
Maybe I misunderstood the question. With that URI you would need to be
connecting as shown bellow:
and the stream name would be:
Thanks Bob. Oddly enough it'll work with the s in the connection url or the stream name. Boggles. The legacy player url parser we're using had it as part of the connection. Your tip helped point me to what the real problem was -- needing to strip the trailing .flv.
Ah, that was another confusing part to me as well. Not sure if you
were doing vod or live - normally those legacy uri's are live but I
wasn't completely sure if that was what you were going for. Glad to