Free summer session software for linux

Distrust is a Firefox extension which hides surfing trails that the browser leaves behind.
AKA Private Browsing.
Once turned on this extension monitors FireFox for its activities.
Once turned off Distrust will remove history items cache and cookies that were used during the distrust session.
Main features:
- Disable the cache. (Both regular and SSL)
- Set the cookies to live until the end of the session.
- Clean up the history from item that were added after it was activated.
- Clean up the downloaded items, from the download manager, that were added after it was activated.

AmarokFS-session is an Amarok script that lets you start your "Amarok" from KDM with "AmarokFS" in fullscreenmode, then you have a dedicated session only for "Amarok".

gnome-session package is free software and is part of the GNOME project.
Contained here are
- the GNOME session manager
- the GNOME session manager configuration program
- and several other session management related utilities.

Lemonldap::Portal::Session is a Perl extension for Lemonldap websso.

SYNOPSIS

use Lemonldap::Portal::Session;

my $paramxml = $test->{DefinitionSession} ; # $test is the result of XML parsing
my $obj = Lemonldap::Portal::Session->init ($paramxml,entry =>$entry) ;

Lemonldap::Portal::Session is a parser of XML description of session to keys,values of hash .

It is a piece of lemonldap websso framework . see eg directory for implementation .

Catalyst::Plugin::Session::CGISession is a Perl module to use CGI::Session for persistent session data.

SYNOPSIS

use Catalyst qw{ ... Session::CGISession ... };

MyApp->config->{session} = {
expires => 3600,
rewrite => 1,
};

$c->session->{user_email} = quibble@dibble.edu;

# Later, in another following request:

$smtp->to( $c->session->{user_email} );

This plugin provides the same functionality as the original Session::FastMmap plugin but uses the CGI::Session module for the session data management.

The motivations to develop this plugin were:

provide better session data expiration handling, as is available through the CGI::Session module
provide an easier migration to Catalyst for applications that have been using CGI::Session and its param() and other methods
allow Windows users to avoid the workarounds needed to make Cache::FastMmap work

The difference in session expiration between this plugin and Session::FastMmap is small but important. CGI::Session resets the expiration time limit on every access to the session. A one day time limit means the session data disappears 24 hours after the last request using that session. With Session::FastMmap the limit would be 24 hours after the first request, when the session is created.

While this plugin adds some functions and methods beyond those available with Session::FastMmap, new development most likely should avoid using these features. Try to use only the common feature, session(), to stay compatible with Session::FastMmap and other future session plugins.

App::Session can represents a sequence of multiple events perhaps executed in separate processes.

SYNOPSIS

# ... official way to get a Session object ...
use App;
$session = App->context();
$context = $session->session(); # get the session

# any of the following named parameters may be specified
$session = $context->session(
);

# ... alternative way (used internally) ...
use App::Session;

A Session class models the sequence of events associated with a use of the system. These events may occur in different processes.

For instance, in a web environment, when a new user arrives at a web site, he is allocated a new Session, even though he may not even be authenticated. In subsequent requests, his actions are tied together by a Session ID that is transmitted from the browser to the server on each request. During the Session, he may log in, log out, and log in again. Finally, Sessions in the web environment generally time out if not accessed for a certain period of time.

Conceptually, the Session may span processes, so they generally have a way to persist themselves so that they may be reinstantiated wherever they are needed. This would certainly be true in CGI or Cmd Contexts where each CGI request or command execution relies on and contributes to the running state accumulated in the Session. Other execution Contexts (Curses, Gtk) only require trivial implementations of a Session because it stays in memory for the duration of the process. Nonetheless, even these Contexts use a Session object so that the programming model across multiple platforms is the same.

CGI::Application::Plugin::Authentication::Store::Session is a session based store.

SYNOPSIS

use base qw(CGI::Application);
use CGI::Application::Plugin::Session;
use CGI::Application::Plugin::Authentication;

__PACKAGE__->authen->config(
STORE => Session,
);

This module uses a session to store authentication information across multiple requests. It depends on the CGI::Application::Plugin::Session plugin being present. Actually, it only requires that there be a session method in the CGI::Application module that will return a valid CGI::Session object.

METHODS

fetch

This method accepts a list of parameters and fetches them from the session.

save

This method accpets a hash of parameters and values and saves them into the session.

delete

This method accepts a list of parameters and deletes them from the session.

Session Manager allows you to save and restore the state of all windows.

Session Manager saves and restores the state of all windows - either when you want it or automatically at startup and after crashes. Additionally it offers you to reopen (accidentally) closed windows and tabs. If youre afraid of losing data while browsing - this extension allows you to relax...

This extension replaces SessionSaver and Tab Mix Plus session manager. It stores more data than both of them and should be more reliable in saving and restoring. Although it is not recommended to have more than one session related extension installed, Session Manager is compatible at least with Tab Mix Plus.