view release on metacpan or  search on metacpan

SecureState.pm  view on Meta::CPAN

As far as threading is concerned, CGI::SecureState (the actual module)
is thread-safe as long as you provide it with an absolute path to the
state file directory or if you do not change working directories in
mid-stream.  This does not mean that it is necessarily safe to use
CGI::SecureState in an application with threads, as thread-safety may
be compromised by either Crypt::Blowfish or Digest::SHA1.  Check these
modules to make sure that they are thread-safe before proceeding to
use CGI::SecureState in an application with threads.

Until I can do more tests, assume that there is precisely zero
support for either threading or unicode.  If you would like to
report your own results, send me a note and I will see what I
can do about them.

Many previous limitations of CGI::SecureState have been
removed in the 0.3x series.


CGI::SecureState requires: