Production client-side code really shouldn't have documentation in. It is
usually taken out by a build script to save bandwidth - the same reason as
why the javascript is "badly formatted" and "obfuscate", it'll probably be
packed or minified.

J

On Jan 9, 2008 9:42 AM, Andy <[EMAIL PROTECTED]> wrote:

> On 06/01/2008, James Cridland <[EMAIL PROTECTED]> wrote:
> > this list (and this thread in
> > particular) is precisely because we -do- want people knowing how as much
> of
> > this works as possible:
>
> Them tell me how it works!
>
> The HTML looks like it was designed to be hard to read, was this the case?
> On many other sites all you have to do is "view source", Ctrl-F,
> ".flv" and you find the URL needed for the stream.
>
> The BBC version is split across multiple config files loaded through
> large amounts of badly formatted javascript (including one long
> section that has had all the line breaks removed!)
>
> I tried the XBox forums but it was rather confusing.
>
> Someone at the BBC wrote this webpage yes? Did they document their
> work, if not is the BBC going to have maintenance problems if the guy
> quits? If so then if the BBC really wants people to know how this
> stuff works gives us a public URL to the document.
>
> And while your at it the documents for the protocols (both the
> streaming version and download version) would be extremely helpful.
> The RTMP link provided appears to be based on reverse engineering and
> guess work.
> Documentation of the actual protocol the BBC is using would be
> preferable, so hand that over.
>
> Apart from the actual HTML itself how much documentation has the BBC
> itself released to help us?
> None as far as I can see. Why?
> Why force us to read through pages of HTML and script?
> Why not just put the URLs in an XML file and gives us the address?
> Forcing people to "screen scrape" proves the BBC does not really care
> about getting iPlayer working. Screen scraping is extremely fragile.
> Changes in the page can cause huge problems.
> The fact the HTML/Javascript code was put through obfuscation
> techniques also proves the BBC isn't trying to help. If you are
> helping why did you obfuscate code?
>
>
>
> > I admire your negativity towards everything posted here, but do cut us
> some
> > slack:
>
> I am only negative when the BBC's actions are negative.
>
> Here's a suggestion:
> Stop putting barriers in peoples way.
> Stop obfuscating code.
> Stop using protocols that are known only to one entity who says "no
> embedded use"
> Start releasing some real documentation.
>
> > we're trying to help as much as we can.
>
> I have told you some of the details that would help me, and probably
> others.
> Instead of actually helping you have decided to force people to resort
> to reverse engineering.
>
> I think the biggest thing people want is you NOT TO USE RTMP.
> It's a major pain to get working if you can't use Adobe Flash and if
> you read the EULA there are lots of cases when you can't.
>
> While your "helping" get a Linux download version released, including
> source code.
> Many of these exotic devices can have Linux run on them, so you could
> have a full iPlayer on them if the BBC DID THEIR JOB RIGHT.
>
> > If you want to bash the BBC,
>
> I will congratulate the BBC when it does something right.
> Sadly I am still waiting.
>
> If you take public money the public has the right to criticise you.
> In non-publicly funded companies if the customer is paying for
> something then you can't just tell them get lost and build something
> that's not what they want. Oddly that's what the BBC has done.
>
>
> 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]/
>

Reply via email to