|
Jifty::Request is a canonical internal representation of an incoming Jifty request. This document discusses the ins and outs of getting data from the web browser (or any other source) and figuring out what it means. Most of the time, you wont need to worry about the details, but they are provided below if youre curious. This class parses the submission and makes it available as a protocol-independent Jifty::Request object. Each request contains several types of information: actions A request may contain one or more actions; these are represented as Jifty::Request::Action objects. Each action request has a moniker, a set of submitted arguments, and an implementation class. By default, all actions that are submitted are run; it is possible to only mark a subset of the submitted actions as "active", and only the active actions will be run. These will eventually become full-fledge Jifty::Action objects. state variables State variables are used to pass around bits of information which are needed more than once but not often enough to be stored in the session. Additionally, they are per-browser window, unlike session information. continuations Continuations can be called or created during the course of a request, though each request has at most one "current" continuation. See Jifty::Continuation. (optional) fragments Fragments are standalone bits of reusable code. They are most commonly used in the context of AJAX, where fragments are the building blocks that can be updated independently. A request is either for a full page, or for multiple independent fragments. See Jifty::Web::PageRegion..
|
Windows Software
Albina Merfyn - I find this to be really easy to use. I can...
