Kiss!
- Write the "answer" as a directory name at a particular place in the file system.
Say /usr/shared/appname/cache/xxxxxx/
- Applications reading the data simply glob the path /usr/shared/appname/cache/*.
They get back a single name that is the answer to the question.
If the readers need to be able to tell how fresh the answer is, they can stat the modified time.
No locking involved.
- The "writing" script, uses the atomic nature of rename to update the directory name at the appropriate times.
No locking involved.
If the answer is too big to fit into a directory name, then use a file with a well-known name.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
