Headings can be transferred:header ("Expires: Mon, 26 Jul 1997 05:00:00 GMT"); header ("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); header("Cache-Control: no-cache, must-revalidate"); header("Pragma: no-cache"); But I don't use that kind of thing, because there's never been a problem.For crypts, the type parameters used /style.css?<?= intval(microtime(1)) ?>

Keep it in the OBD system. How depends on the degree of consistency. If in general, keep close to those data that are synchronization units. For example, if you sync one post, keep it as part of the post. If you sync up all the poser posts, put it to the laser or a separate table that would refer to the laser. If you synchronize all posts, keep in a separate table (if synchronized properties are large, you can create a common table for all).

My file cash, made it on a virtual hosting. The CodeIgniter Framing Library, the essence is simple, in the case of PLO, it is possible to change the way and use it.<?php class Cache{ private $_cacheFolder; public function __construct(){ $this->_cacheFolder = 'app/cache/'; } /** * чтение * * @param mixed $key */ public function load($key){ $file = $this-&gt;_cacheFolder . md5($key); if(file_exists($file)){ $data = unserialize(file_get_contents($file)); if(time() &lt;= $data['time'] + $data['ttl']){ return $data['data']; } unlink($file); } return FALSE; } /** * добавление * * @param mixed $key * @param mixed $data * @param mixed $time */ public function save($key, $data, $time){ $file = $this-&gt;_cacheFolder . md5($key); $content['data'] = $data; $content['time'] = time(); $content['ttl'] = $time; if(file_put_contents($file, serialize($content))){ @chmod($file, 0777); return TRUE; } return FALSE; } /** * удаление * * @param mixed $key */ public function remove($key){ $file = $this-&gt;_cacheFolder . md5($key); if(file_exists($file)){ unlink($file); } } }

I've got the same problem. Ficcill in such a way: var imageUrl = $rootScope.site + $rootScope.avatar; $scope.decachedimageUrl = imageUrl + '?decache=' + Math.random(); UPD: salivation for chiel or text by example: $scope.rma = {}; var num = Math.floor(Math.random() * 90000) + 10000; var dateVal = num + "-" + $rootScope.date; // Склеиваем случайное число с входящей датой console.log('date val :'); console.log(dateVal); var datePartials = dateVal.split("-"); // Делим что получилось на части $scope.rma.purchaseDate = datePartials[1]; // В этом примере часть с индексом [1] - год var newDate = new Date().getFullYear(); // Смотрим какой сейчас год $scope.rma.purchaseDate = newDate - datePartials[1]; // Получаем число лет, разницу между входящей датой и текущей. //Например количество полных лет пользователя.

Cashing does not cover external resources. In other words, the enumerators, the guidance services, and the like, you can't clash because you can't influence the server's response, which is not under your control. The problem with the outside violets is not solved, you don't turn them into a server, and in the case of scruples like Google Analytics, it's impossible. If you want to score 100 points in Speed Insights' toolbox, either turn off the extra side of the crypts or perform a similar function on your own server.

Yes, repository and escrow are two responsibilities. However, in your second example, the kashing repository is https://ru.wikipedia.org/wiki/Proxy_(%D1%88%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD_%D0%BF%D1%80%D0%BE%D0%B5%D0%BA%D1%82%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F) to a simple repository (to merge them with a common interface) and there's no violation of SRP.Under responsibility in SRP Martin meant that there was a need to change the class - the reason for this need should be one. In the second example, the class will have one reason to change - the change of algorithm/cashing method. If the repository changes (the change of OBD, nosql, feather repositories in memory for youth test, etc.), this will have no effect on the cashing class.Class which organizes the interaction of two classes (i.e. https://ru.wikipedia.org/wiki/%D0%A4%D0%B0%D1%81%D0%B0%D0%B4_(%D1%88%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD_%D0%BF%D1%80%D0%BE%D0%B5%D0%BA%D1%82%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F) ) https://stackoverflow.com/questions/17807770/does-the-facade-pattern-violate-srp ♪ In this case, the logic of interaction between classes will be assumed.

Go Clearly faster, but for each instas, there's no possibility of a charding, after the rebut or fall of the instas, the cordial data will be missing, and there's also problems with the garbage collector in the 1.4x versions of the big maps. https://github.com/golang/go/issues/9477 (in version 1.5, all right, in 1.6, even bigger, there's a prefabricator working fast, but to get rid of a check by a bush collector, it's like, https://github.com/allegro/bigcache ) Redis Slower, but this is not so much to compare with requests for a basic database, there is the possibility of a charding, when the instas falls, the kees rise from the disk, a lot of possibilities over the top, and it is also a well-known KVS independent of IP, which will make it easier to get help.If product growth and development are planned, it will be necessary to frustrate. Redis♪

This is built at the web server level. Github Pages has no access to any configuration files, so nothing can be done. The same picture is found in some of the hosts, and we need to clarify it in advance.

Exactly what the name says.LRU - Least Recently Used - https://ru.wikipedia.org/wiki/%D0%90%D0%BB%D0%B3%D0%BE%D1%80%D0%B8%D1%82%D0%BC%D1%8B_%D0%BA%D1%8D%D1%88%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F#Least_recently_used_.28.D0.92.D1.8B.D1.82.D0.B5.D1.81.D0.BD.D0.B5.D0.BD.D0.B8.D0.B5_.D0.B4.D0.B0.D0.B2.D0.BD.D0.BE_.D0.BD.D0.B5.D0.B8.D1.81.D0.BF.D0.BE.D0.BB.D1.8C.D0.B7.D1.83.D0.B5.D0.BC.D1.8B.D1.85.29 ♪In your case, there are 100 positions in the neck. When there is no free space for a new recording, one of the available records shall be removed release

Got it. It's not Drupal as such, it's the kash on proxy serves. In the commentaries, they wrote about the browser's kash, which gave me a push to think. Cash stayed not only in the browser, but also on the intermediate servers, that's it. Cache-control: publici.e., when the first appeal was made, the proxy-server recalled a page with all the headings, including the reappointment of the dock (what I didn't take when I was making the publicity of the kash). The fact that the reason was that he couldn't have known for a long time, because if the page came back from the browser cash, it's indicated in the headline description, kash proxy doesn't differ from server treatment other than time.I don't quite understand why the identifier of the session is changing at the main (after the logic, the user will be redirected not to the main) - but it's a little more gradual.

MySQL-Kashing is not only the clashing of the result, but also the request itself, therefore with the cash, when recordings are heated in Redis if the sql query is already in MySQL-Kash, the data velocity will be much faster than the MySQL-Cash disconnected. Based on the description, it is necessary to understand how often MySQL is used and how the logic of redis-a data is built.

So?from django.core.cache import cache key = 'key' data = cache.get(key) if data is None: # update cache now... cache.set(data, key, 3600)

For example, there is a request for OBD, its results can be retained in Redis in the form of JSON, and the following applications will already take it from Redis and, where necessary, make the cash disable. - How right is that?100 per cent, but the timely handicap of the kash is a pretty big shuttle.Is it worth keeping data in JSON?In fact, I'm a little bit of a Corobiter to keep this line, but there's no specific choice, and it doesn't have to affect anything at all.We sometimes need a page encrypted not only in JSON, but a piece or a whole HTML. - Is it right to keep these pieces in Redis?No, you have a SPA, all the rendering should be on the client.There's an idea to implement a session-storage in Redis, how to do it right Is that right or not? How will it be better?If your session is considered to be a permanent repository, it's not right because Redis is not meant to keep the data permanently (whether he can turn the data on the CD from time to time). Instead, it is better to organize a two-tier (or even three-level) repository from Redis-OBD (In-Memory - Redis-OBD in the case of tri-level interconnections).In which case should the cash be recorded in the CD files?Normally, there's a database. There's a way to throw the results of the heavy requests so that all their legs can be seen, but even in this case, I'd organize an interim Redis-Slave.Shouldn't we be drinking what's described in redis?The more you hang in the cash, the better, but you watch the number of melted operational memory from time to time.Maybe there's some guidance on working with high-load sockets or something on the basis of such a project.Remember two things.The project has to be scaled up horizontally, i.e. simple addition of new servers. It follows that changes on one server should be visible to all others (this is achieved through the use of one Redis and OBD)There's a thing like dogpile effect, which means a bunch of users who at the same time request the same resource. In the case of the three-level repository described above, 100 simultaneous users are not detected in the cash and are laminated (all 100) to the OBD. In the case of 20 simultaneous connections in the OBD system and each request takes 30ms, the last user will receive data not before 150ms (which ideally is, in fact, there would be a considerable amount of data.Oh.That's not good.

It depends on very many factors. How exactly do you reconstruct fragments when you move from the tab to the tab? Generally speaking, the following are:For fragments. Keep it. onSaveInstanceState The collection that goes to the adapter, onViewCreated if savedState!=null You're rebuilding.For the Vews, respectively, in the Assitis or Fragment, you keep a mob with the tabs and a collection sheet and you set it up if there's something on the adapter, if you don't, you're downloading it from the Internet.It's so hard to tell you without a specific code.

It's a frequent problem of starting Symfony developers. You don't use ACL. In the end, the rights you're giving to the folder app/cache Nothing is inherited, and all further changes inside the folder do not guarantee that your console will have the same rights to the files in this folder as the user of the web server.Read carefully the section on the installation of the director's rights. http://symfony.com/doc/current/book/installation.html#checking-symfony-application-configuration-and-setup ♪If you have a problem with ACL, you can always write in. app/console♪ web/app.php♪ web/app_dev.php manually installing rights to all files being created:umask(0002); // 0775 // или umask(0000); // 0777

Or something like that!<meta http-equiv="Cache-control" content="no-cache"> <meta http-equiv="Pragma" content="no-cache"> <meta http-equiv="Expires" content="-1">

First, the difficulties will start if your kash starts working in a multi-point environment. HashMap Not thread-safety class, and therefore it will be necessary to synchronize access operations or to use stationary collections.Secondly, if your annex consumes a lot of memory and the kash is heavy, then it may happen that when memory begins to end, GC will not removing objects from the kash. It will therefore need to be implemented on weak references(s)SoftReference/WeakReference)Thirdly, if the velocity of search in the cash is critical, it is worth thinking about choosing another Hash Table implementation. HashMap It's not the most effective structure with a large number of objects with the same footprint.

A picture of 50 times on one page with the same loading method will only be downloaded once! Not 50.If you have to put a picture in the client's browser, it's usually enough. Cache-Control: private, max-age=60 a more detailed reading http://ruhighload.com/post/%D0%9A%D0%B5%D1%88%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5+Cache-control

Incorrect calls expire_fragment♪And if you have the Rels of version 4.0 or above, it's enough to write: - cache @post do It will itself be updated when the model is updated in @post.

Well, it wouldn't be bad to know what for. The solution may be very different from the type of task.There are several ways:Simple kash in hard drive files, often enough for simple tasks.Use memcachedThe use of redis, a powerful tool, can be remembered by different data structures or simply a text, considering what purpose. But we need to pre-construct so we don't write a hard drive. We can set an expiration date.