Apache2::ClickPath::Store Apache2::ClickPath::Store module can use Apache2::ClickPath sessions to store information.
Download

Apache2::ClickPath::Store Ranking & Summary

Apache2::ClickPath::Store Tags

information Perl module sessions store information

Apache2::ClickPath::Store Description

Apache2::ClickPath::Store module can use Apache2::ClickPath sessions to store information. Apache2::ClickPath::Store module can use Apache2::ClickPath sessions to store information.SYNOPSIS LoadModule perl_module ".../mod_perl.so" PerlLoadModule Apache2::ClickPath::Store ClickPathStoreDirectory "some_directory" ClickPathStorePath "/uri" ClickPathStoreTimeout 300 ClickPathStoreCleanupInterval 60Apache2::ClickPath::Store and Apache2::ClickPath::StoreClient can be used in conjunction with Apache2::ClickPath to store arbitrary information for a session. The information itself is stored on a WEB server and accessed via HTTP. Apache2::ClickPath::Store implements the server side and Apache2::ClickPath::StoreClient the client side.The system is designed to work for a WEB server cluster as well as for a single WEB server. Assuming there is a cluster consisting of N machines all using Apache2::ClickPath to provide session identifiers. Then each WEB server can manage its own information store running on the same server or all servers can use a single or a few dedicated information stores. The information store is simply another WEB server or < Location > running Apache2::ClickPath::Store.Here each WEB server manages its very own information store: +-------------------------+ | +----------------+ | | | Cluster | | | | | | | | +-------------+| | access the server's very own | | | Server 1 || | information store | | | || | | | | *--------+ | | | StoreClient || | | | *--------+ | | |.............|| | | | | || | access a foreign +------>| Info Store || | information store | | || | | +-------------+| | | | | | ... | | | | | | +-------------+| | | | Server N || | | |.............|| | | | || | +------>| Info Store || | | | | || | | | +-------------+| | | +----------------+ | +-------------------------+And here is a centralized information store: here work Apache2::ClickPath and Apache2::ClickPath::StoreClient +----------------+ | Cluster | and here | | Apache2::ClickPath::Store | +-------------+| +------------+ | | Server 1 || | | | | || info store | | | | *----------------------->| Info | | | || access | | | +-------------+| +-------------->| store | | | | | | | ... | | | | | | | +------------+ | +-------------+| | | | Server N || | | | || | | | *--------+ | | || | +-------------+| +----------------+ProtocolThe store offers a simple HTTP-form interface to get and set information items. It doesn't matter whether GET or POST requests are used. The data is accepted in multipart/form-data or application/x-www-form-urlencoded. The following CGI-parameter control how the data is accessed:acan be either get or set and defines whether the data is read or written.sthe session identifier. All data is stored in a session-oriented way. Normally this is a session that was generated by Apache2::ClickPath but in principle it could be any string not containing a slash (/). It must not start with a hash sign (#).kwithin a session data is accessed via a key. The key is a string of characters all matching Perl's w regular expression. A particular data item is identified by combination of session and key.vthis parameter is valid only if a is set. It contains the actual data to be written.Normally the store answers a request with HTTP status code 200 (OK). In case of a read operation the response body contains just the data item. The HTTP content-type is set to application/octet-stream. In case of a write operation the string ok is returned with the content-type set to text/plain.If something went wrong it is indicated by the HTTP status code. The store returns the following codes:500 Server Errorthis indicates a configuration error. Maybe the data directory doesn't exist or is not writeable.400 Bad Requestan invalid key or session identifier was used.404 Not Foundthe data item identified by the combination of session and key was not found. If the item had once existed then it was possibly hit by a timeout.Requirements:· Perl Requirements: · Perl

Apache2::ClickPath::Store Related Software