Apache2-POST200

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

        For best performance create an index on the "key" column.

        The "data" column must be able to hold a variable size data block.
        The maximum size can be limited using "Post200DataBlockSize". If
        "Post200DataBlockSize" is not used the size completely depends on
        your response handlers. If possible use a BLOB type as "data"
        column.

        Although not used by the module it makes sense to add a 3rd column
        to the table. It should be a timestamp column with the default
        attribute set to "now()". Without it it's difficult to decide which
        records can be deleted.

        With a MySQL database a suitable table is created by:

         create table p200 (
           session varchar(50) primary key unique not null,
           data blob,
           tm timestamp not null default 'now'
         );
         create index p200_tm_idx on p200(tm);

lib/Apache2/POST200.pod  view on Meta::CPAN


For best performance create an index on the C<key> column.

The C<data> column must be able to hold a variable size data block. The
maximum size can be limited using C<Post200DataBlockSize>. If
C<Post200DataBlockSize> is not used the size completely depends on your
response handlers. If possible use a BLOB type as C<data> column.

Although not used by the module it makes sense to add a 3rd column to the
table. It should be a timestamp column with the default attribute set to
C<now()>. Without it it's difficult to decide which records can be deleted.

With a MySQL database a suitable table is created by:

 create table p200 (
   session varchar(50) primary key unique not null,
   data blob,
   tm timestamp not null default 'now'
 );
 create index p200_tm_idx on p200(tm);



( run in 0.230 second using v1.01-cache-2.11-cpan-de7293f3b23 )