gnash-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-dev] [PATCH] User-specific tmp directory and auto-removal of


From: Takashi Iwai
Subject: Re: [Gnash-dev] [PATCH] User-specific tmp directory and auto-removal of swf files
Date: Wed, 23 Aug 2006 20:00:08 +0200
User-agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (Sanjō) APEL/10.6 MULE XEmacs/21.5 (beta25) (eggplant) (+CVS-20060326) (i386-suse-linux)

At Wed, 23 Aug 2006 09:53:02 -0600,
Rob Savoye wrote:
> 
> Takashi Iwai wrote:
> 
> 
>   Btw, there is already support for a ~/.gnashrc file, you'd just have
> to add the support for the additional config setting, since it has to
> get parsed out of the file.

OK, will check it.

> >>   I haven't seen any pages with multiples of the same name, but I guess
> >> it's possible. We could use mkstemp() to make them all unique, but when
> >> the change to make the plugin stream the movie while downloading is
> >> done, movies won't be downloaded at all anymore except optionally.
> > 
> > Sorry, I don't understand this downside well.  Could you elaborate?
> 
>   Their are changes being made so the Gnash standalone player can read a
> movie from stdin via pipes. This will let the plugin send the data in
> chunks to the player while the browser is reading the stream. The goal
> here is it makes movies start playing while the rest of the movie is
> still loading. At that point the need for the downloaded movie will be
> gone. The only reason the plugin downloads a movie to /tmp is because
> Gnash was limited to only working with disk files. This was the easiest
> way to make the plugin work at that time.

Ah, this would be a neat feature.  Yes, in that case, it's basically
no problem about the temp dirs/files, indeed.


Takashi




reply via email to

[Prev in Thread] Current Thread [Next in Thread]