yes maybe but I store some private info on user session
I prefer to keep on the server.
and if I save iops I loose on network bandwidth and speed , no ?
I think about Dancer::Session::Redis do you test it ?
Hugues.
Le 08/05/2014 11:40, Nick Knutov a écrit :
use utf8::all may help.
D::Session::Cookie is faster (and saves iops/SSD)
08.05.2014 14:35, Stefan Hornburg (Racke) пишет:
On 05/08/2014 10:21 AM, Hugues wrote:
Hello
I found a strange problem with my D1 app
in my config.yml
charset: "UTF-8"
template: "template_toolkit"
engines:
template_toolkit:
encoding: 'utf8'
start_tag: '[%'
end_tag: '%]'
serializer: 'JSON'
session: 'JSON'
all characters with accent appear encoding
cat sessions/142370789218895586385667162125359748.json | jq .
"MemoAction": "2014-05-08 001 RESET-ARRET/MARCHE ���©���©���© \r\n",
"MemoPanne": " 2014-05-08 001 PB BATTERIE ���©���©���©���© \r\n"
if I use session: 'YAML' in config.yml all is ok
cat sessions/295483594817224343797619192129361122.yml
MemoAction: "2014-05-08 001 RESET-ARRET/MARCHE éééé \r\n"
MemoPanne: " 2014-05-08 001 PB BATTERIE \r\n2014-05-08 001 PB BATTERIE ééé \r\n"
I do something special with json session ?, I tried to encode/decode without
success
( all this text come from web user )
That is most likely a bug with Dancer::Session::JSON.
Sawyer?
BTW: I would recommend to use a faster file based session engine for production.
Regards
Racke
_______________________________________________
dancer-users mailing list
[email protected]
http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
