Documente Academic
Documente Profesional
Documente Cultură
Introduction
The Nette SafeStram protocol for file manipulation guarantees atomicity and isolation of every file
operation.
Why is it actually good? Let's start with a simple example, where we repeatedly write the same
string to the file and then read it:
$counter = 1000;
while ($counter--) {
file_put_contents('file', $s); // write it
$read = file_get_contents('file'); // read it
if ($s !== $read) { // check it
echo 'Strings are different!';
}
}
It may seem that the echo 'Strings are different!' command can't ever get executed. The
opposite is true. Try to run this script in two browsers simultaneously. The error occurs almost
immediately.
It's because the code is not safe when performed repeatedly at the same time (ie, in multiple
threads). And that is nothing unusual on the Internet, where several people often connect to one
website at the same time. Therefore, it's very important to ensure that your application can handle
multiple threads at once - that it's thread-safe, because native PHP functions are not. Otherwise,
you can expect data loss and strange errors occuring.
How to ensure, that functions like file_get_contets or fwrite behave atomically? The SafeStream
protocol offers a secure solution, so we can atomically manipulate files through standard PHP
functions. To register this protocol install SafeStream via Composer. After that, you just need prefix
the filename with nette.safe:// :
fwrite($handle, 'Nette Framework'); // for now, the data is written into a temporary
You can of course use all the familiar functions, such as:
https://github.com/nette/safe-stream 1/2
05/11/2018 GitHub - nette/safe-stream: SafeStream: atomic and safe manipulation with files via native PHP functions.
file_put_contents('nette.safe://test.txt', $content);
$ini = parse_ini_file('nette.safe://autoload.ini');
SafeStream guarantees:
If you write to an existing file in the ' a ' mode (append), SafeStream creates it's copy and only after
successfully writing it renames it to the original name. Write in this mode is therefore more
resource-consuming than in other modes.
Installation
The recommended way to install is via Composer:
https://github.com/nette/safe-stream 2/2