Re: [cowiki-dev] Re: [Issue 219] coWiki always keeps temporary files in htdocs
Paul Hanchett <[email protected]> Mon, 12 Sep 2005 13:12:48 -0700
| Newsgroups | gmane.comp.php.cowiki.devel |
|---|---|
| Message-ID | <[email protected]> |
--------------020504080101070609070100
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Daniel T. Gorski wrote:
>On 12 Sep 12:22, Paul Hanchett wrote:
>
>
>>How does coWiki separate it's files from other applications on the
>>machine?
>>
>>
>
>It mainly uses a part of a MD5 digest of the string that represents the path
>to the current installation. Different installations have different paths ->
>different MD5 digests.
>
>Additionally there are few other information encoded in a temporary file
>name, depending on what it is good for. This information could be "user
>template", "user language" and the "user id" ... So an temporary could have
>a name like this:
>
> coWiki_3C3E5B83_customdocrecent_876de65a_default_65535_en.iso-8859-1
>
>
I guess I had seen the code (or at least the file) and figured something
*smart* was going on...
>
>
>
>>Will coWiki running on different processing threads experience a
>>race condition?
>>
>>
>
>It didn't yet, as different coWiki installation do not share anything (no
>data, no code).
>
>
Isn't it possible that under load that server might allocate additional
threads to service user requests? If that happens, could two threads be
servicing the same coWiki instance and one delete or modify the cache
out from under the other?
Doesn't seem likely, but...
Paul
--------------020504080101070609070100
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="mid20050912194848.GN23827@bantha" type="cite">
<pre wrap="">On 12 Sep 12:22, Paul Hanchett wrote:
</pre>
<blockquote type="cite">
<pre wrap="">How does coWiki separate it's files from other applications on the
machine?
</pre>
</blockquote>
<pre wrap=""><!---->
It mainly uses a part of a MD5 digest of the string that represents the path
to the current installation. Different installations have different paths ->
different MD5 digests.
Additionally there are few other information encoded in a temporary file
name, depending on what it is good for. This information could be "user
template", "user language" and the "user id" ... So an temporary could have
a name like this:
coWiki_3C3E5B83_customdocrecent_876de65a_default_65535_en.iso-8859-1
</pre>
</blockquote>
I guess I had seen the code (or at least the file) and figured
something *smart* was going on...<br>
<blockquote cite="mid20050912194848.GN23827@bantha" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">Will coWiki running on different processing threads experience a
race condition?
</pre>
</blockquote>
<pre wrap=""><!---->
It didn't yet, as different coWiki installation do not share anything (no
data, no code).
</pre>
</blockquote>
Isn't it possible that under load that server might allocate additional
threads to service user requests? If that happens, could two threads
be servicing the same coWiki instance and one delete or modify the
cache out from under the other?<br>
<br>
Doesn't seem likely, but...<br>
<br>
Paul<br>
<br>
</body>
</html>
--------------020504080101070609070100--