How to Install and Uninstall perl-Apache-Session Package on openSuSE Tumbleweed

Last updated: November 21,2024

1. Install "perl-Apache-Session" package

This guide covers the steps necessary to install perl-Apache-Session on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                perl-Apache-Session
            
                    
    
    Copied

2. Uninstall "perl-Apache-Session" package

In this section, we are going to explain the necessary steps to uninstall perl-Apache-Session on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                perl-Apache-Session
            
                    
    
    Copied

3. Information about the perl-Apache-Session package on openSuSE Tumbleweed

Information for package perl-Apache-Session:
--------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-Apache-Session
Version : 1.94-1.17
Arch : noarch
Vendor : openSUSE
Installed Size : 175.2 KiB
Installed : No
Status : not installed
Source package : perl-Apache-Session-1.94-1.17.src
Upstream URL : https://metacpan.org/release/Apache-Session
Summary : Persistence framework for session data
Description :
Apache::Session is a persistence framework which is particularly useful for
tracking session data between httpd requests. Apache::Session is designed
to work with Apache and mod_perl, but it should work under CGI and other
web servers, and it also works outside of a web server altogether.
Apache::Session consists of five components: the interface, the object
store, the lock manager, the ID generator, and the serializer. The
interface is defined in Session.pm, which is meant to be easily subclassed.
The object store can be the filesystem, a Berkeley DB, a MySQL DB, an
Oracle DB, a Postgres DB, Sybase, or Informix. Locking is done by lock
files, semaphores, or the locking capabilities of the various databases.
Serialization is done via Storable, and optionally ASCII-fied via MIME or
pack(). ID numbers are generated via MD5. The reader is encouraged to
extend these capabilities to meet his own requirements.
A derived class of Apache::Session is used to tie together the three
following components. The derived class inherits the interface from
Apache::Session, and specifies which store and locker classes to use.
Apache::Session::MySQL, for instance, uses the MySQL storage class and also
the MySQL locking class. You can easily plug in your own object store or
locker class.