On Sat, 28 Mar 2009 12:55:03 -0700, ohRonaldo
Yes - the Player, not the Browser. They are entirely different
applications, and you cannot extrapolate from one to t'other.
Are you sill typing this into the browser address bar ?
My advice is not to, and use the player embedded in a web page, with a
fullscreen option. Otherwise you're leaving the end-user experience
open to only-working-on-your-dev-machine, leading to unhappy
customers, no invoices paid, and so forth.
Using HTTP *explicitly*, in some circumstances, yes. There's no
problem in actually enabling HTTP playback, as that may be the only
way to get your content past restrictive corporate or .edu firewalls
The best plan is to leave the player and the media server to correctly
negotiate the most effective delivery method available, rather than
second guessing the work of years of media streaming experts who made
protocol rollover possible.
You fluked it. Now install VideoLAN player - or another player (like
RealPlayer) which also knows how to handle these URLs, and see what
the experience is. Now multiply that by 100x for end users with a wide
variety of misconfigured / non-default systems.
They'll phone YOU (more likely your boss or your customer) when it
doesn't "work", and the only details you will have is "It doesn't
wotk", and you're hosed (and possibly looking for a new job)
Are you close to retirement ?
Cool, hope it works out ;-))
Cheers - Neil
Digital Media MVP : 2004-2009