[Top][All Lists]

[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 17:37:07 +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:21:06 -0600,
Rob Savoye wrote:
> Takashi Iwai wrote:
> > At Wed, 23 Aug 2006 09:01:08 -0600,
> > Another candidate is a directory under $HOME.  I chose
> > /tmp/gnash-$USER because $HOME might be shared via NFS (like my
> > system) where confliction among machines may happen.
>   Or you might want to share, since currently downloaded movies are used
> for debugging. This is why I like letting the user decide, and we can
> default to /tmp/gnash-$USER if they don't care.

Sure, a dynamic configuration via ~/.gnashrc would be more flexible

I see the benifit of keeping the downloaded swf files, especially for
debugging, too.  So, the automatic-removal behavior of my previous
patch should be conditioned via a config file, too.

> > But, the swf file name is anyway not guaranteed to be unique, so far.
> > If you open a web page (or pages) with multiple flashes with the
> > very same file name, it wouldn't work properly...
>   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?


reply via email to

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