File: stash.rst

package info (click to toggle)
iceweasel 38.8.0esr-1~deb7u1
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 1,578,008 kB
  • sloc: cpp: 4,134,345; ansic: 1,765,754; python: 324,651; java: 233,700; asm: 138,937; xml: 98,298; sh: 82,895; makefile: 21,621; perl: 17,235; objc: 4,014; yacc: 1,968; lex: 1,179; exp: 499; pascal: 479; lisp: 228; awk: 152; ruby: 82; sed: 43; csh: 31; ada: 16; php: 1
file content (31 lines) | stat: -rw-r--r-- 1,045 bytes parent folder | download | duplicates (9)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Stash
=====

Object for storing cross-request state. This is unusual in that keys
must be UUIDs, in order to prevent different clients setting the same
key, and values are write-once, read-once to minimise the chances of
state persisting indefinitely. The stash defines two operations;
`put`, to add state and `take` to remove state. Furthermore, the view
of the stash is path-specific; by default a request will only see the
part of the stash corresponding to its own path.

A typical example of using a stash to store state might be::

  @handler
  def handler(request, response):
      # We assume this is a string representing a UUID
      key = request.GET.first("id")

      if request.method == "POST":
          request.server.stash.put(key, "Some sample value")
          return "Added value to stash"
      else:
          value = request.server.stash.take(key)
          assert request.server.stash.take(key) is None
          return key

:mod:`Interface <stash>`
------------------------

.. automodule:: wptserve.stash
   :members: