Free winter summer sessions software for linux

Destiney DB Sessions Script provides a small connection to the database in order to assist the PHP developer.

Destiney DB Sessions script is some simple database connection code to assist the PHP applications developer in handling secure, efficient, database driven PHP sessions within a larger PHP application.

In simplest terms Destiney DB Sessions is a drop-in replacement for the default PHP session handling and does not require editing the php.ini whatsoever.

MultiSessionX is a fast user switching implementation for X11 utilizing VNC for persistent sessions. It provides a choosable menu via xdialog or xmessage. It supports Linux, FreeBSD, and Irix.
Main features:
- Support for xdialog and xmessage (xmessage provided for legacy support -- use xdialog instead). Support planned for zenity.
- Maintain multiple user logins from a single terminal without logging users out.
- Reconnect to sessions from another terminal.
- Multiple sessions per-user.
- Mulitple connections to a single session. (vnc -shared)
- Allows creation of non-persistent sessions -- starts window manager normally to support features not available through VNC (high-speed video, opengl)
Note: use with xdialog and an X11 login manager can be very similar to the behavior AND visual appearance of Windows 2003 with Terminal Services. I should note that this project was started early 2002, well before Windows 2003 was released! Just in case you were wondering ;-)
Licensed under the general BSD license (no advertising clause).
Version restrictions:
- VNC has a lot of bugs and limitations. For instance, it does not support OpenGL or XV visuals. "Non-persistent" sessions provided as work-around. Also, VNC "messes up", causing visual artifacts.
- Does not work with Zenity at all, not even its gdialog emulation

VNC Session Manager provides a disconnected session manager for VNC.

VNC Session Manager adds the necessary glue code between VNCs two execution modes, enabling XDM-based login to disconnected sessions. This gives a Terminal Services-like login for Unix-based VNC servers.

POE::Session is a Perl module for event driven abstract state machine.

SYNOPSIS

# Import POE::Session constants.
use POE::Session;

POE::Session->create(

# Inline or coderef states.
inline_states => {
state_one => &coderef_one,
state_two => sub { ... },
},

# Plain and mapped object states.
object_states => [
$object_one => [ state_three, state_four, state_five ],
$object_two => { state_nine => method_nine },
],

# Plain and mapped package states.
package_states => [
$package_one => [ state_six, state_seven, state_eight ],
$package_two => { state_ten => method_ten },
],

# Parameters for the sessions _start state.
args => [ argument_zero, argument_one, ... ],

# Initial options. See the option() method.
options => %options,

# Change the sessions heap representation.
heap => [ ],
);
Other methods:
# Retrieve a sessions unique identifier.
$session_id = $session->ID;

# Retrieve a reference to the sessions heap.
$session_heap = $session->get_heap();

# Set or clear session options.
$session->option( trace => 1, default => 1 );
$session->option( trace );

# Create a postback, then invoke it and pass back additional
# information.
$postback_coderef = $session->postback( $state_name, @state_args );
$postback_coderef->( @additional_args );

# Or do the same thing synchronously
$callback_coderef = $session->callback( $state_name, @state_args );
$retval = $callback_coderef->( @additional_args );

POE::Session combines a runtime context with an event driven state machine. Together they implement a simple cooperatively timesliced thread.
Sessions receive their timeslices as events from POE::Kernel. Each event has two fields, a state name and a session identifier. These fields describe the code to run and the context to run it in, respectively.

Events carry several other fields which will be discussed in the "Predefined Event Fields" section.

States are re-entrant since they are invoked with their runtime contexts. Although its not usually necessary, this re-entrancy allows a single function to be bound to several different sessions, under several different state names.
As sessions run, they post new events through the Kernel. These events may be for themselves or other sessions, in which case they act as a form of inter-session communications. The Kernel can also generate events based on external conditions such as file activity or the passage of time.

POE provides some convenient built-in states with special meanings. They will be covered later on in the "Predefined States" section.

DB_eSession provides a class that securely stores PHP sessions in a MySQL database.
DB_eSession is a feature-packed PHP class that stores session data in a MySQL database rather than files. It is powerful, designed with security in mind, and is easy to utilize.
The code contains lots of comments, and it comes with full documentation and examples of how to use the class including a basic authentication login/logout process.
It includes member functions useful (to webmasters) for monitoring or viewing, deleting, and altering sessions validity for the case of locking one or more sessions upon detection of unauthorized use.
Main features:
- General features:
- Stores session data in a MySQL table using PHPs built-in session handler.
- Built-in handling of session expiration and cleanup.
- Supports the changes of session related configuration settings (inc. PHP5).
- Allows for normal or persistent MySQL database connections.
- Access to opened MySQL resource connection to use in your script.
- Accepts a passed database resource link to use as the DB connection.
- Supports session IDs between 12 and 32 characters long.
- Custom or changeable database, table and column names.
- An option to create new session IDs (you supply, class or PHP builds).
- Can initiate buffered output (using ob_start) within the class.
- A session_start() automatically initiated within the class.
- Can send Cache-Control: header output within the class (fixes IE6 bug).
- Ability to retrieve a specific sessions expiration date and time.
- Retrieve current session life setting in seconds or minutes.
- Retrieve a numeric total of the number of active and inactive sessions in table.
- Facility to make assignment and retrieval of session variables easier.
- Ability to create manual URIs and links that includes session name and ID.
- The ability to retrieve what the MySQL server version number is.
- An adequate form of encode/decode member functions are included and used automatically when libmcrypt is not installed.
- Security features:
- Standard user inactivity time-out handled automatically.
- Absolute user logoff time-out capability (session will be terminated no matter what after a number of designated minutes/seconds have elapsed).
- Ability to lock and unlock a particular session or all sessions. When a session is made locked it is immediately not available for use.
- User to session verification using IP address and browser information.
- Security level (code) clearance for each session/web page.
- Encrypt/decrypt as desired each session field.
- Encrypt/decrypt an extra session field to compare against original (to detect against possible tampering).
- Encrypt/decrypt the whole session data in the table (essentially obscuring session variable names in table). Can be used in combination with per session field encryption, resulting in double encryption security.
- A new encryption Initialization Vector is created every time values change.
- Ability to manually delete a particular session or all sessions.
- The users IP address and web browser is recorded as part of the session for tracing information.
- Other features:
- Support for multiple language error and warning messages.
- Support of a default language as well as current active language settings.
- Basic or detailed (with SQL syntax) error/warning reporting.
- Buffered error and warning messages.
- Option for class to stop execution or not upon encountering an error/warning. Class can display errors/warnings automatically or control in your script.
- Can select font color and size separately for error and warning messages.
- Code has lots of comments and formatted within 82 characters wide.
- Full documentation (only provided in English) is included.
- Code use examples provided, including a basic authentication (login/logout) process.
- SQL text file provided for creating the MySQL session table.

PHP::Session is a Perl module to read / write PHP session files.

SYNOPSIS

use PHP::Session;

my $session = PHP::Session->new($id);

# session id
my $id = $session->id;

# get/set session data
my $foo = $session->get(foo);
$session->set(bar => $bar);

# remove session data
$session->unregister(foo);

# remove all session data
$session->unset;

# check if data is registered
$session->is_registered(bar);

# save session data
$session->save;

# destroy session
$session->destroy;

# create session file, if not existent
$session = PHP::Session->new($new_sid, { create => 1 });

PHP::Session provides a way to read / write PHP4 session files, with which you can make your Perl application session shared with PHP4.

If you like Apache::Session interface for session management, there is a glue for Apache::Session of this module, Apache::Session::PHP.

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.

PHP::Session::DB is a Perl module to read / write PHP sessions stored in databases.

SYNOPSIS

use PHP::Session::DB;

my $session = PHP::Session::DB->new($id, { DBUSER => $dbuser, DBPASSWD => $dbpasswd, DBNAME => $dbname });

# session id
my $id = $session->id;

# get/set session data
my $foo = $session->get(foo);
$session->set(bar => $bar);

# remove session data
$session->unregister(foo);

# remove all session data
$session->unset;

# check if data is registered
$session->is_registered(bar);

# save session data
$session->save;

# destroy session
$session->destroy;

# create a new session, if not existent
$session = PHP::Session->new($new_sid, { %dbvars, create => 1 });

PHP::Session::DB provides a way to read / write PHP4 sessions stored on databases, with which you can make your Perl application session shared with PHP4.