In case of token timeout orientdb should send back an error and after
that drop the connection for some internal technical reasons.
so it shouldn't timeout, you should get an error, so please submit some
issue about it on both projects, with test cases if possible ;)
bye
On 01/04/15 21:39, David Carr wrote:
I'm running orientdb server 2.0.5 with Ostico/PhpOrient and am storing
the orientdb connection token in the user's php web server session so
that we don't have to authenticate against orientdb using
username/password with every pageview. It all works well until too
much time elapses between pageviews and the server token expires
unexpectedly. When this happens the end user initiates a new pageview
and the socket_read to orientdb just hangs and the page eventually
times out while the user is waiting.
Any suggestions regarding how I can avoid this poor user experience?
If I knew in advance when the server token was going to expire then I
could expire the token in the web server session as well and force an
orientdb username/password connection at the correct time.
OR if orientdb didn't time out but responded with an "expired token"
message then perhaps I could catch that error and force a
username/password connection.
OR if I could deserialize the token and parse the expected expiration
datetime from it then I might be able to force a new username/password
connection at the right time.
Unfortunately I've been unsuccessful with all of these approaches.
--
---
You received this message because you are subscribed to the Google
Groups "OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
