Thanks for your comments also.

Yes .flv and other video files will play with Lightttpd using normal
media players, for example, using JW Player in kpax/static/
mediaplayer.swf . It is even possible to use players while the actual
video file is hosted on another server to where the main site and
player is hosted. It is really more of a browser issue unless seek
based streaming is desired.

The video files I host on http://www.zgus.com are on Amazon S3 servers
because the traffic costs are lower this way and because VPS disk
space usage is kept lower. In fact, as mentioned in
http://groups.google.com/group/web2py/msg/e273fa31c779c44c ,  I think
it would be a good idea to allow large uploaded files to automatically
transferred across to other servers. Keeping large files on other
severs is the 'enterprise way'. There is mature python infrastructure,
s3cmd, to allow file transfer to Amazon S3 servers, as indicated in
the link.

There is another meaning for streaming which basically means being
able to seek anywhere into the video file without downloading the
entire file into the browser cache. Lighttpd supports this type of
streaming 'out of the box'. Apache does not. YouTube uses Lighttpd and
supports this type of streaming (provided the video file has the
necessary meta data).

Having a web server that supports seek based streaming is not enough.
For this type of streaming a compliant media player is required and
video files need to have meta data installed. There is a coherent
presentation on this type of streaming, on what needs to be done to
video files and a video example at 
http://flowplayer.org/plugins/streaming/pseudostreaming.html

John Heenan

On Feb 14, 1:44 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
> Very well done.
>
> Did you ever try streaming files with lighttpd? For example serving
> via download a large video file, larger than ram? (kpax comes with an
> example of streaming). Does it work well?
>
> Massimo
>
> On Feb 13, 1:42 am, John Heenan <johnmhee...@gmail.com> wrote:
>
> > As requested I have placed a howto on web2pysplices 
> > athttp://www.web2pyslices.com/main/slices/take_slice/57
>
> > I have written a considerable preface to clarify issues and to
> > indicate why we should pay attention to issues concerned with keeping
> > memory use low.
>
> > John Heenan
>
> > On Feb 13, 2:41 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > I think this is an excellent point.
>
> > > > My data demonstrated a 40MB memory solution is feasible.
>
> > > > I am absolutely amazed and disappointed I cannot get such simple
> > > > points gracefully acknowledged by a self styled 'expert' and by the
> > > > moderator.
>
> > > The reason I suggested opening a new thread was to eliminate the
> > > digression.
> > > Would you write a short howto on web2pyslices on how to achieve this
> > > small memory footprint?
> > > Eventually it could become a section in the book.
>
> > > Massimo

-- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en.

Reply via email to