view release on metacpan or  search on metacpan

README  view on Meta::CPAN

        ACCAT
        AATTG

        ## If you don't know how many tokens you need at the start of the pipeline...
        $ session-token --infinity | ... | head

DESCRIPTION
    This module came about because I found myself frequently running the
    following command:

        $ perl -MSession::Token -E 'say Session::Token->new->get'
        YwXYXGLMMnudk33MbClseQ

    Before I wrote Session::Token I used to run the following command:

        $ openssl rand -base64 16
        fjxhL/LmZEUQ+NCldQbHgA==

    They both perform essentially the same task however "session-token" has
    various advantages:

bin/session-token  view on Meta::CPAN

    AATTG

    ## If you don't know how many tokens you need at the start of the pipeline...
    $ session-token --infinity | ... | head


=head1 DESCRIPTION

This module came about because I found myself frequently running the following command:

    $ perl -MSession::Token -E 'say Session::Token->new->get'
    YwXYXGLMMnudk33MbClseQ

Before I wrote L<Session::Token> I used to run the following command:

    $ openssl rand -base64 16
    fjxhL/LmZEUQ+NCldQbHgA==

They both perform essentially the same task however C<session-token> has various advantages:

It is more flexible regarding the alphabet used since it supports any alphabet that L<Session::Token> does via the C<--alphabet> switch. Its default alphabet is the (IMO) nice base-62 versus C<openssl rand>'s base-64.