<div dir="ltr">i don't mind being wrong :)<br>thanks Eero, it was the principle more than the specifics I was trying to indicate however.<br><br><div class="gmail_quote">On Thu, Oct 16, 2008 at 3:46 PM, Eero Tamminen <span dir="ltr"><<a href="mailto:eero.tamminen@nokia.com">eero.tamminen@nokia.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<div class="Ih2E3d"><br>
<br>
ext gary liquid wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
have you considered caching the downloaded file to disk and reading from<br>
there using the standard function?<br>
<br>
This would give you the obvious benefit of allowing offline usage and faster<br>
requerying.<br>
There isn't an infinite amount of memory available and having to download<br>
images everytime could cause user angst.<br>
<br>
I believe /tmp is mapped to real memory and not the flash drive, so would<br>
not cause real problems and wouldn't be much slower (someone can confirm<br>
this?)<br>
</blockquote>
<br></div>
This is a no-no. The system /tmp is a RAM-disk with 1/2MB max size<br>
and it's used by all applications. It's intended for _small_ (few KB)<br>
temporary files. For larger or more permanent[1] things one should<br>
use $TMPDIR i.e. /var/tmp which is on Flash.<br>
<br>
[1] See the Filesystem Hierarchy Standard:<br>
<a href="http://www.pathname.com/fhs/" target="_blank">http://www.pathname.com/fhs/</a><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Even though it may require a little bit more time to organise a cache file<br>
plan, it may be worth it in the end?<br>
</blockquote>
<br>
<br></div></div><font color="#888888">
- Eero<br>
</font></blockquote></div><br></div>