Re: [cowiki-dev] Re: [Issue 219] coWiki always keeps temporary files in htdocs
Paul Hanchett <[email protected]> Mon, 12 Sep 2005 12:22:36 -0700
| Newsgroups | gmane.comp.php.cowiki.devel |
|---|---|
| Message-ID | <[email protected]> |
--------------040804050400070302010104
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Daniel T. Gorski wrote:
>On 12 Sep 11:41, Paul Hanchett wrote:
>
>
>>>What could be done by the installer, is to set the TEMP-path in the
>>>core.conf file explicitly to the session path used by PHP internally
>>>(session.save_path), which per definition should be always secure and not
>>>reachable by an user agent.
>>>
>>>
>
>
>
>>>Letting the user (and not an admin) to decide where the temporary files
>>>should go, is basically not a good idea - stikes me. regards dtg
>>>
>>>
>
>
>
>>Well, we have two types of users-- An admin who will be able to
>>configure paths as needed, and a user of a hosting service who may or
>>may not how enough rights. Correct?
>>
>>
>
>Correct.
>
>
>
>>For example, my own ISP gives me a public_html where there is a virtual
>>host configured. How would I configure the temp directory outside of
>>that?
>>
>>
>
>You would also need an includes/ directory somewhere. So the
>permissions/access would need to be set accordingly for a /tmp/ directory
>then. Right.
>
>As I said above: We take the PHP temporary directory where PHP saves its
>sessions to save our temporary data too - the PHP session directory is
>always configured and writable for the httpd or the PHP process; and it's
>always out of the access of an user agent.
>
>Different coWiki instances on the same machine won't interfere(!), even if
>they use the same direcory for sessions, because coWiki uses different names
>for its tmp-files which are unique for each installation on the same host.
>
>
This seems OK to me, except that the delete cache option just blindly
deletes everything in coWiki's temp directory, doesn't it? How does
coWiki separate it's files from other applications on the machine? Will
coWiki running on different processing threads experience a race condition?
I too would prefer using the "standard" solution to the problem if we
can do it properly. :-) The "roll-your-own" approach is appropriate
when there is not agreed upon solution. When there is, it just makes
the multitude of applications harder to understand. :-)
Paul
--------------040804050400070302010104
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Daniel T. Gorski wrote:
<blockquote cite="mid20050912190341.GM23827@bantha" type="cite">
<pre wrap="">On 12 Sep 11:41, Paul Hanchett wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">What could be done by the installer, is to set the TEMP-path in the
core.conf file explicitly to the session path used by PHP internally
(session.save_path), which per definition should be always secure and not
reachable by an user agent.
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Letting the user (and not an admin) to decide where the temporary files
should go, is basically not a good idea - stikes me. regards dtg
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">Well, we have two types of users-- An admin who will be able to
configure paths as needed, and a user of a hosting service who may or
may not how enough rights. Correct?
</pre>
</blockquote>
<pre wrap=""><!---->
Correct.
</pre>
<blockquote type="cite">
<pre wrap="">For example, my own ISP gives me a public_html where there is a virtual
host configured. How would I configure the temp directory outside of
that?
</pre>
</blockquote>
<pre wrap=""><!---->
You would also need an includes/ directory somewhere. So the
permissions/access would need to be set accordingly for a /tmp/ directory
then. Right.
As I said above: We take the PHP temporary directory where PHP saves its
sessions to save our temporary data too - the PHP session directory is
always configured and writable for the httpd or the PHP process; and it's
always out of the access of an user agent.
Different coWiki instances on the same machine won't interfere(!), even if
they use the same direcory for sessions, because coWiki uses different names
for its tmp-files which are unique for each installation on the same host.
</pre>
</blockquote>
This seems OK to me, except that the delete cache option just blindly
deletes everything in coWiki's temp directory, doesn't it? How does
coWiki separate it's files from other applications on the machine?
Will coWiki running on different processing threads experience a race
condition?<br>
<br>
I too would prefer using the "standard" solution to the problem if we
can do it properly. :-) The "roll-your-own" approach is appropriate
when there is not agreed upon solution. When there is, it just makes
the multitude of applications harder to understand. :-)<br>
<br>
Paul<br>
<br>
</body>
</html>
--------------040804050400070302010104--