Skip to content

Commit

Permalink
README: Update for changes in storing of form fields.
Browse files Browse the repository at this point in the history
  • Loading branch information
pfalcon committed Nov 15, 2018
1 parent 54d9354 commit 5d039d8
Showing 1 changed file with 15 additions and 2 deletions.
17 changes: 15 additions & 2 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ Bottle and Django. Note that this does not mean particular "compatibility"
with Flask, Bottle, or Django: most existing web frameworks are synchronous
(and threaded), while picoweb is async framework, so its architecture is
quite different. However, there is an aim to save porting efforts from
repeatitive search & replace trials: for example, when methods do similar
repetitive search & replace trials: for example, when methods do similar
things, they are likely named the same (but they may take slightly different
parameters, return different values, and behave slightly differently).

Expand All @@ -96,12 +96,25 @@ provided).
Last point is questionable conveniences. For example, both Flask and Bottle
provide special objects to handle form/get parameters, with features
like "if request variable has only one value, the value is returned directly;
otherwise, list of values is returned". However, Python standard library
otherwise, list of values is returned".

.. raw:: html

<strike>

However, Python standard library
provides function parse_qs(), which always returns array of values (based
on the fact that any request variable may have more than one value). Given
2 choices, picoweb follows the interface of the standard library, instead of
providing extra wrapper class on top of it.

.. raw:: html

</strike>

Changed in 1.5: now normal single-valued fields store the value directly, list is used only
for multi-valued fields. (Reasons: convenience, reduced memory usage.)


API reference
-------------
Expand Down

0 comments on commit 5d039d8

Please sign in to comment.