On 21/01/2008, Iain Wallace <[EMAIL PROTECTED]> wrote:
> Back to RTMP. I was looking at the documentation and some of the code
> for RTMP with a view to maybe porting it into this script. It's really
> quite nasty!
If only there was a nice simple document. Unfortunately it all appears
to be reverse engineered. And thus there are parts that are clear
guess work (or just plain not defined. Like the randomish data used
near the beginning of the handshake).
At the risk of going wildly of topic. Is there anywhere that describes
all this business with remote procedure calls? Does this mean an RTMP
client needs to have a full interpreter for some programming language
and isn't allowing unauthenticated remote entities to make function
calls on your system a "bad idea". I can think of lots of unfriendly
function calls one would not want people to make.
> Any extensions to this script from me are likely going
> to be calls to apps importing the rtmp.c written for Gnash.
PHP calls to a C library? (Sorry been a very long time since I did
PHP, many years, ah the good old days )
I was trying to write a little something in Java to basically
determine what programs where available, what versions where available
and some details about them.
Ran into one massive problem. Well 2, one I have more important
commitments that come first, and 2: How does one obtain a list of
whats on iPlayer without spidering the entire A to Z each time? Is
there something one can put in the filter URL parameter that says
"only programs added since X"? Or a way of listing more than 6 entries
at a time?
Oh and I think Mr Forrester may have been a tad dishonest (possibly
unintentionally) when claiming RTMP and FLV where just like PDF and
that anyone can create readers for them. PDF is an ISO standard! I
can't find formal standards for RTMP and FLV, did I miss them
somewhere? Tried RFC/IETF and ISO, neither have anything.
Also would it be possible to get the stream in a sensible format?
If you ever want iPlayer on a mobile use a viable format. For
reference Android (Google's Mobile Platform) supports MPEG4 and H.264.
How about a stream in one of those formats?
The biggest problem with getting iPlayer on exotic devices is the BBC
lack of public documentation and no simple way of finding out things
that should be documented fully somewhere.
As an example here is some questions I had after only a few hours work
on some Java code:
The versions listed on the HTML page have a date. What timezone is
this meant to be in?
Am I correct in thinking the month is 0 indexed? And that the order
is: Year, Month, Day_Of_Month, Hour, Minutes, Seconds
With Hour being expressed using the 24 hour clock?
And how precisely is Midnight represented?
And which elements are optional in the XML files?
Which elements can be repeated?
What are the different values of the id field in the element error
returned when a stream is invalid? What do these values mean and when
do they occur?
What are the acceptable characters in the PID?
What are the acceptable characters in the Token field?
How precisely does the filter argument in the URL for the iPlayer A to
Z actually work?
It appears to be some kind of query language, what are the names of
fields and operators?
Some of those would have been answered by the XML Schemes.
So if you really are interested in exotic platforms, then maybe
telling people what they need to know would help!
Andy
--
Computers are like air conditioners. Both stop working, if you open windows.
-- Adam Heath
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/[email protected]/
