mORMot Open Source

igors233

Member

Registered: 2012-09-10

Posts: 241

Handling session problems on client side

I'm using SMS for client side development and have an issue when session expires for example, server will send 403 as expected but I cannot get that information on client side. OnError callback procedure as is defined now (TSQLRestEvent) just have client (TSQLRestClientURI) as argument and it's not possible to get OutStatus or returned result from it.
I think it would be good to define a different OnError event (not shared with OnSuccess) and to pass more information to it, OutStatus and returned result.

Also it would be good to have general OnStatus/OnError event handler defined in TSQLRestClientURI that would be called before passed OnSuccess/OnError callbacks, it would allow easy centralized handling of all errors (404, 403, 401, 202...) and all received responses (it might get handy in certain situations).

Last edited by igors233 (2016-05-17 19:13:34)

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,666

Website

Re: Handling session problems on client side

Good idea.

Could you please create a feature request ticket?
Connect to http://synopse.info/fossil/reportlist then click on "Login" and log in anynomously (the forum login won't work), then create a feature request ticket.