Phil Ehrens wrote:
Carl Karsten wrote:
Martin Guy wrote:
Plan A: generate a .mpg every time someone clicks. that's lame.
Plan B: add the jpg's to one big .mpg as the jpgs come in. then slice off
the
last X frames and serve that up.
How about Plan C: store the jpgs and generate a new last-whatever mpg
every time a new frame comes in, rather than when people click.
Kinda depends on how CPU intensive it is, and how much the server admin
cares. (not my box.) I am guessing the 'generate content' will be 10x
faster than 'serve over 700k dsl connection' so I am not too concerned with
making the user wait for the file to be generated after they click.
But whatever is easier to get functioning - would be good to have something.
Don't forget to NOT update when the current image is less than some
delta from the last image. Only do the really intensive part when
there's a reason to.
How can that be determined, and how do I accommodate the missing frame in the
sequence?
> And you probably never actually want to update
just because a user clicked anyway... That's silly.
Depends on site traffic. If the page only gets a 20 or so hits a day, why
bother generating the mpg every min (1440 times a day)
Carl K
