Hi Vidura, On Fri, Sep 11, 2015 at 12:08 PM, Vidura Gamini Abhaya <[email protected]> wrote:
> Hi Rajith, > > 'Got a couple of questions on this. > > *) How different would this be to Boxcarring in term of the design? I > presume the plan is to create the collated payload within the client itself > and not rely on the session management of the transport as much? > Yes you are correct, that is the plan, We have faced some issues recently because of this session management part, because we are relying on tomcat session management. In the boxcarring request, what we do is store incoming requests which comes after "begin_boxcar" request and execute those accumulated requests in the final "end_boxcar" request. So in new approach, we are going to do the same, break full request into multiple operations and execute one by one. And as same as boxcarring, it will return the result of last operation. > *) Semantically, is it any different to Boxcarring in it's usage at the > client? > Yes, instead of sending multiple requests, client needs to build full request at once and send. > > *) What benefits would this feature have over Boxcarring (other than the > obvious) ? > Basically it addresses the Obvious part, where as clients need to send each request with same session when using boxcarring. And it is logical to send single request if we know all the operations and and parameters beforehand. Thanks, -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
