Sympa::Request - Requests for operation
use Sympa::Request; my $request = Sympa::Request->new($serialized, context => $list); my $request = Sympa::Request->new(context => $list, action => 'last');
Sympa::Request implements serializable object representing requests by users.
- new ( [ $serialized, ] context => $that, action => $action, key => value, ... ] )
- Constructor. Creates a new Sympa::Request object.
A new instance of Sympa::Request, or undef, if something went wrong.
- new_from_tuples ( key => value, ... )
- Constructor. OBSOLETED. Creates Sympa::Request object from paired options.
- dup ( )
- Copy constructor. Gets deep copy of instance.
- to_string ( )
- Serializer. Returns serialized data of object.
- cmd_line ( [ canonic => 1 ] )
- Instance method. TBD.
- handler ( )
- Instance method. Name of a subclass of Sympa::Request::Handler to process request.
- get_id ( )
- Instance method. Gets unique identifier of instance.
Context and metadata¶
Context and metadata given to constructor are accessible as hash elements of object. They are given by request spool. See "Context and metadata" in Sympa::Spool::Auth for details.
These are accessible as hash elements of objects. There are attributes including:
- Custom attribute connected to requested action.
- Display name of user sending request.
- E-mail of user who sent the request.
Sympa::Request object includes number of slots as hash items: metadata, context and attributes. Metadata including context are given by spool: See "Marshaling and unmarshaling metadata" in Sympa::Spool.
Logically, objects are stored into physical spool as serialized form and deserialized when they are fetched from spool. Attributes are encoded in "X-Sympa-*:" pseudo-header fields.
See also "Serialization" in Sympa::Message for example.
Sympa::Request::Collection, Sympa::Request::Handler, Sympa::Request::Message, Sympa::Spool::Auth.
Sympa::Request appeared on Sympa 6.2.10.