Sponsored Content
The Lounge What is on Your Mind? Individual Risk Management (Personal IT Security) and Browser Cache Management Post 303033321 by Neo on Wednesday 3rd of April 2019 07:46:19 AM
Old 04-03-2019
Quote:
Originally Posted by bakunin

...

Cookies are little files a web server places at the client side which can be queried by the server later. In most cases these are used for harmless functions - after all, HTTP does not create a "session" but works rather like a mail exchange. HTTP consists of independent messages going back and forth between sender and receiver and if one wants to provide lasting context (this is what sets apart "sessions" from "messages") either the web server has to remember it - which would lead to exhaustion of resources on the server side in a very short time - or the server has to have a way to offload that to the client. This was the original rationale for creating cookies and in general storing web content on the client side.
First. let me help you clarify.

Cookies are generally not "queried" by a server. Cookies are sent to the server with each page (that belong to the same cookie domain) as part of the standard HTTP request.

If you open any web dev tool, like Google Chrome Web Dev Tools (but it is the same with each major browser), you will see the cookies are sent with each page, not requested by the server.

Sorry, I just wanted to be technically correct.
 
App::Cache(3pm) 					User Contributed Perl Documentation					   App::Cache(3pm)

NAME
App::Cache - Easy application-level caching SYNOPSIS
# in your class: my $cache = App::Cache->new({ ttl => 60*60 }); $cache->delete('test'); my $data = $cache->get('test'); my $code = $cache->get_code("code", sub { $self->calculate() }); my $html = $cache->get_url("http://www.google.com/"); $cache->set('test', 'one'); $cache->set('test', { foo => 'bar' }); my $scratch = $cache->scratch; $cache->clear; DESCRIPTION
The App::Cache module lets an application cache data locally. There are a few times an application would need to cache data: when it is retrieving information from the network or when it has to complete a large calculation. For example, the Parse::BACKPAN::Packages module downloads a file off the net and parses it, creating a data structure. Only then can it actually provide any useful information for the programmer. Parse::BACKPAN::Packages uses App::Cache to cache both the file download and data structures, providing much faster use when the data is cached. This module stores data in the home directory of the user, in a dot directory. For example, the Parse::BACKPAN::Packages cache is actually stored underneath "~/.parse_backpan_packages/cache/". This is so that permisssions are not a problem - it is a per-user, per-application cache. METHODS
new The constructor creates an App::Cache object. It takes three optional parameters: o ttl contains the number of seconds in which a cache entry expires. The default is 30 minutes. my $cache = App::Cache->new({ ttl => 30*60 }); o application sets the application name. If you are calling new() from a class, the application is automagically set to the calling class, so you should rarely need to pass it in: my $cache = App::Cache->new({ application => 'Your::Module' }); o directory sets the directory to be used for the cache. Normally this is just set for you and will be based on the application name and be created in the users home directory. Sometimes for testing, it can be useful to set this. my $cache = App::Cache->new({ directory => '/tmp/your/cache/dir' }); o enabled can be set to 0 for testing, in which case you will always get cache misses: my $cache = App::Cache->new({ enabled => 0 }); clear Clears the cache: $cache->clear; delete Deletes an entry in the cache: $cache->delete('test'); get Gets an entry from the cache. Returns undef if the entry does not exist or if it has expired: my $data = $cache->get('test'); get_code This is a convenience method. Gets an entry from the cache, but if the entry does not exist, set the entry to the value of the code reference passed: my $code = $cache->get_code("code", sub { $self->calculate() }); get_url This is a convenience method. Gets the content of a URL from the cache, but if the entry does not exist, set the entry to the content of the URL passed: my $html = $cache->get_url("http://www.google.com/"); scratch Returns a directory in the cache that the application may use for scratch files: my $scratch = $cache->scratch; set Set an entry in the cache. Note that an entry value may be an arbitrary Perl data structure: $cache->set('test', 'one'); $cache->set('test', { foo => 'bar' }); directory Returns the full path to the cache directory. Primarily useful for when you are writing tests that use App::Cache and want to clean up after yourself. If you are doing that you may want to explicitly set the 'application' constructor parameter to avoid later cleaning up a cache dir that was already in use. my $dir = $cache->directory; AUTHOR
Leon Brocard <acme@astray.com> COPYRIGHT
Copyright (C) 2005-7, Leon Brocard LICENSE
This module is free software; you can redistribute it or modify it under the same terms as Perl itself. perl v5.12.3 2009-12-08 App::Cache(3pm)
All times are GMT -4. The time now is 01:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy