Forum Moderators: open
Otherwise, the best way is to encode it into a format suitable for streaming over the Internet. Which format? Well, there's really three choices:
Real
Windows Media
Quicktime
Once they are in one of the above formats - they can be streamed either via a media server (which is the better choice if you have clients connecting on both dial-up and broadband, as the MPEG can be encoded to cater for both, with the server providing the appropriate quality according to the available bandwidth), or using HTTP from a standard web server (where you can only use a single bandwidth rate).
The encoders for the above formats can be found on the appropriate sites of Real [realnetworks.com],Windows Media [microsoft.com] and Quicktime [apple.com].
HTH,
JP
A media server generally can run on the same server as a web server, as it uses different ports. Note - it can be a memory hog! You'll more than likely need root/administrator access to install it. Windows Media Server only runs on a Win2K (maybe NT4 too) platform, though the new Real Helix Server will stream WM content too, which is nice. Having just installed Helix last week on one of my boxes, it seems to do a good job of it too!
Re: b) - This is probably the major difference. Whereas a normal web server will simply (unintelligently) serve whatever it is told to fetch by the requesting client, a media server will talk to the client and deliver the content at a speed the client can reliably receive it. If the user is on a modem, the media server can serve out the content so that neither the audio or video breaks up, but instead the quality of both picture & sound will be decreased when compared with a faster link such as broadband. Also, whilst a client is viewing the content - if the available bandwidth decreases, the server can switch the content delivery to a lower quality so the clients' viewing is unaffected by pauses.
If you were to stream the file from a normal web server - the bonuses are no need to install a server and go through the installation procedure and worry about lessened security, but you'd have to build into your web interface an option to choose the connection quality before viewing, so the appropriate content can be delivered. Also, the client is more likely to experience pauses.
It all depends on the application and the viewing audience as to which route you choose.
Hope I'm not waffling too much!
JP