Thanks, sounds good. Thanks for the prompt reply.

Also, how are you generating the OSESSIONID's? My concerns is, if we allow 
client control over the OSESSIONIDs (storing them on the client-side) then 
there could be an attack where people guess the OSESSIONIDs to try to fish 
for access to 
someone else's account. With a very active database, this can be a concern.

Here are 2 samples.

OS1406072996074-5691658514500952040
OS1406073156931-2054454498811953916

Part of the number seems to be based on timestamp. What are your thoughts 
on this?


On Tuesday, July 22, 2014 6:23:11 PM UTC-4, Lvc@ wrote:
>
> Hi Simon,
> To avoid the cost of re-opening the database you should be sticky to the 
> same server (until it become unreachable).
>
> Please consider also to execute multiple operation in one call by using 
> the SQL Batch: 
> https://github.com/orientechnologies/orientdb/wiki/SQL-batch
>
> Lvc@
>
>
>
> On 22 July 2014 23:50, Simon L <[email protected] <javascript:>> wrote:
>
>> Hi there,
>>
>> We have a very large site with tons of users making numerous queries. 
>> We're using Node.JS with Backbone, and OrientDB as the backend DB. 
>> There will be multiple webservers and multiple OrientDB servers.
>>
>> What are the recommendations for lowering the overheads of constantly 
>> reconnecting to OrientDB?
>>
>> I was thinking of connecting with the REST API with OSESSIONID. Maybe 
>> there's a better way?
>> We aren't sure about using sticky or non-sticky sessions just yet. We're 
>> open to both options.
>>
>> -- 
>>
>> --- 
>> 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] <javascript:>.
>> 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.

Reply via email to