Hi,
Intuitively, "set" must always set the value, while "update" - only
updates existing
entry (if it exists), but current behavior is exactly the opposite.
Currently, cache_set() in psgi just calls uwsgi_cache_set2() with no
flags set,
and this leads to counter-intuitive result - if key is already in the
cache,
it will be untouched.
On the other hand, cache_update() (if it would exist in psgi and set
update flag),
will always set the key - regardless of its existence (assuming that
flag is set).
Is this intentional behavior?
--
Best regards,
Alexander.
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
