Hi Argh, By per thread you meant per request, right? You should think of how to store credentials to prevent user log in each request.
Best regards, Artem Orobets * Orient Technologiesthe Company behind OrientDB* 2014-07-11 9:57 GMT+03:00 Argh Skwidge <[email protected]>: > Having read the discussion, it seems that the main issue is session > management over the binary protocol, and connection sharing for large > numbers of sessions. > > I'm thinking that if I am using a plocal connection in an embedded > connection these issues don't directly relate to my use model. Assuming I > am using an OrientGraph or ODatabaseDocumentTx per thread, is there > anything else that might trip me up? Memory constraints perhaps? > > > On Friday, 11 July 2014 00:48:14 UTC+12, Artem Orobets wrote: >> >> Hi guys, >> >> It may be used for such purpose, but in some cases you may meet some >> issues. And yeah, there is still no a convenient API for that. >> We still not decided how to change a design to make that 100% supported, >> here <https://github.com/orientechnologies/orientdb/issues/2229> an >> issue where a discussion going on. >> >> Best regards, >> Artem Orobets >> >> * Orient Technologiesthe Company behind OrientDB* >> >> >> -- > > --- > 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.
