Hi Simon, Unfortunately the sessions are not shared between servers, but when OrientDB runs in distributed configuration this would be very easy to have by using Hazelcast to store session map.
Is this the case? Lvc@ On 22 July 2014 23:25, Simon L <[email protected]> wrote: > Hi everyone, > > One challenge is that we will be using multiple servers and load balancing. > > The obvious choice to avoid reconnecting to the DB for each request seems > to be using OrientDB's REST API and pass the OSESSIONID on to the end-user > as a cookie.. > *BUT... *In a multi-server OrientDB cluster, is the OSESSIONID shared > among the OrientDB servers? > > A workaround would be to also add a cookie for the DB server's internal IP > (or network codename, etc). For a number of reasons that's not ideal, but > I'm curious. > > > -- > > --- > 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. > -- --- 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.
