On Mon, 1 Jun 2009, thron7 wrote: >> In general, the /tmp directory on most Unix systems (including Linux) >> should be cleared at reboot. I am surprised to hear that there are >> systems that don't do that. > > For all I can say, Suse doesn't.
I hope Suse at least monitors /tmp/ usage and cleans it out when necessary. > BTW, I didn't finished the sentence starting "Since we are running...", > but it was about running on three OS's, so we are looking for a > cross-platform location (but everybody probably guessed that). I'd guess so too ... :-) >> It seems to make sense to me to configure the cache location in the >> config.json file on a per application basis. This way each developer can >> decide what he wants to do. > > Well, as I said this is always possible. Burak wanted it to be explicit in > the config.json. Do you think the same, or are you satisfied with an > implicit default - explicit deviation? I think "implicit" always means educated guessing ... I'd rather have it explicetly set (as you suggested in another posting). >> Personally, I think it would make sense to have the cache directory >> default to a directory inside the application tree. > > This was exactly what we wanted to avoid. I can live with a cache location > outside /tmp, eg. in the qooxdoo path, but I would want to retain the > cross-application location, so you have the benefit of cache reuse across > applications. You can always change that in the individual config.json's, > ok?! I hadn't thought about the cross-application use case. I guess this has some merit. I'd suggest to have both settings in the config.json file (one commented out of course and both with appropriate comments). The build system is something most people will not look into very closely at the beginning of using Qooxdoo ... >> Perhaps /var/tmp/ would be more reasonable, although I am not sure if >> there aren't distributions that clear this as well (Ubuntu Jaunty >> doesn't). > > Yeah, I wouldn't want to rely on that too. BTW, I think the Qooxdoo install directory would be a very bad choice. At least in a larger installation (e.g., not just a developers laptop or standalone desktop) the install directory SHOULD NOT be writable by ordinary users. >>> As I said, the solution is as close as your config.json. As for the poor >>> user experience due to automatically erased /tmp directories, I would be >>> interested to learn who else has this issue?! >> >> Just tried my current application with >> >> ./generate source >> >> With cache: 1.592u 0.112s 0:01.76 96.5% 0+0k 1944+0io 0pf+0w >> Without cache: 56.003u 0.956s 1:08.43 83.2% 0+0k 48432+0io 0pf+0w >> >> So this WILL hurt, if the cache is deleted unintentionally. > > Thanks for the metrics, Fritz, but I was not questioning the difference > between cache and no cache, I was asking about the /tmp clearance :). I understood, but the implication is that /tmp being cleared WILL HURT the next time around. Although I agree that Unix/Linux systems don't have to be rebooted all that often, there are still many issues even with the most recent distributions that might require a reboot. Laptops being worse than desktops in my experience, mainly due to (more) exotic hardware. The more recent a laptop the more likely that hibernation and/or other hardware related things might not work properly, requiring a reboot. Here in Switzerland, for example, we have a USB-based GSM-modem that more often than not doesn't come back to life after a suspend (I am not sure about hibernation right now). Very annoying and even more annoying if the Qooxdoo cache would be gone as well ... I guess there is no real good default solution for this problem. But, you could actually ask the user at installation time of the SDK whether s/he wants to have a global cache directory and if so, where it should be. This directory could then be created during installation with the appropriate (/tmp-like) permissions. And then set the default config.json setting appropriately. Cheers, Fritz -- Oetiker+Partner AG tel: +41 62 775 99 03 (direct) Fritz Zaucker +41 62 775 99 00 (switch board) Aarweg 15 +41 79 675 06 30 (mobile) CH-4600 Olten fax: +41 62 775 99 05 Schweiz web: www.oetiker.ch ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
