Hi Dilan, As I understood, Jaggery is running on top of JSP/Servlet structure and use same principles (more like a wrapper to JSP). Session scopes and concurrency also similar to simple Jsp app. Each request will be served by separate thread. So You have to deal with shared resources by keeping that in mind..
PS: Please correct me if I'm wrong.. :) On Wed, Oct 22, 2014 at 7:59 AM, Dilan Udara Ariyaratne <[email protected]> wrote: > Hi All, > > I am just curious to know on "To what extent, Jaggery can deal with > Concurrency Issues". > > For example, if some Jaggery Script is there to handle some file operations > on a shared file or some database operations that we expect to be mutually > exclusive... > > And also about the scope of Jaggery "session" variable: i.e. when the > server is dealing with > multiple concurrent executions of the same Jaggery script, are we dealing > with multiple independent sessions or just one session instance... > > Any Feedback on this would be highly appreciated. > > Thanks. > > *Dilan U. Ariyaratne* > Software Engineer > WSO2 Inc. <http://wso2.com/> > Mobile: +94775149066 > lean . enterprise . middleware > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Dinesh J. Weerakkody* Software Engineer WSO2 Inc. lean | enterprise | middleware M : +94 727 361788 | E : [email protected] | W : www.wso2.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
