Hi Subash, Ah! forgot to discuss this today when we chatted.
Subash the get() itself is a call spanning across multiple tables and for the sake of a DB-neutral implementation we have kept the queries basic. So this means we handle some joins etc at application-level. This is why it has to be transactional. But, I was under the impression that the cache solves this issue altogether with the get() doing nothing @ Embedded Registry level. Isn't this the case or are you talking about first call slow-down? Thanks, Senaka. On Mon, Aug 18, 2014 at 6:36 AM, Subash Chaturanga <[email protected]> wrote: > Hi Senaka et al, > Is there any particular reason for doing $subject ? Because transactional > db connection is always heavy and many applications doing the GET quite > frequently. IMO we should not be doing a read in a transactional manner. > Pls correct me if I am missing something. > > I am referring EmbeddedRegitry#get. > > -- > Thanks > /subash > > *Subash Chaturanga* > Senior Software Engineer & Lead WSO2 Governance Registry > Platform TG; WSO2 Inc. http://wso2.com > Contact: > email: [email protected] > blog: http://subashsdm.blogspot.com/ > twitter: @subash89 > phone: +9477 2225922 > Lean . Enterprise . Middleware > -- *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388; ext: 51736*; *M: +44 782 741 1966 Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
