Hi, These decisions were made during the last meeting I had with the mentors, Kasun Indrasiri and Isuru Udana on 17th June 2015.
- Store the flow in the Message Context and the component details in the db - Create a separate thread to persist the data asynchronously - Generate an unique id for each component in the flow - when accessing the database use the message id and component id as the key - Study more about the flow ending points - Implement a suitable algorithm to represent the flow in more user friendly way - (when the messages are cloning, iterating and aggregating situations) Thanks, On Wed, Jun 10, 2015 at 4:56 PM, Chanaka Sampath Cooray < [email protected]> wrote: > Hi, > > Here are the points we have discussed in the last meeting. > > - Building a proper data structure to store and process the Message > Flow > - Persist the collected data after the Message Flow has completely > finished - Store the data from the data collection points in memory until > the message flow finished > - Store the first generated Message Id as a property in the Message > Context - message id will be changed in some situations, so we can't be > able to track the message flow > - Pay special attention to the mediators extends > from FlowContinuableMediator - Mediators those have branches > - Store the timestamp, payload, headers and property set as the basic > information > > Thanks, > > On Tue, Jun 9, 2015 at 4:20 PM, Isuru Udana <[email protected]> wrote: > >> Hi Chanaka, >> >> Can you please update the thread with notes of the meeting we had >> yesterday ? >> >> On Tue, Jun 2, 2015 at 3:39 PM, Chanaka Sampath Cooray < >> [email protected]> wrote: >> >>> Hi Manuranga, >>> >>> Yes, the data publishing mostly goes through the same log4j flow. But we >>> decided to write the data to the database in our initial discussion. But it >>> is not confirmed yet. >>> >>> Thanks, >>> >>> On Tue, Jun 2, 2015 at 3:27 PM, Manuranga Perera <[email protected]> wrote: >>> >>>> Does this data publishing goes through the same log4j flow? Is the data >>>> collector written as a log4j appender ? >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Chanaka Sampath Cooray* >>> Undergraduate | Department of Computer Science and >>> Engineering,University of Moratuwa >>> Mobile: +94 71 361 4884 >>> E-Mail: [email protected] >>> Linked-In: https://lk.linkedin.com/pub/chanaka-sampath/65/221/102 >>> <https://lk.linkedin.com/pub/chanaka-sampath/65/221/102> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Isuru Udana* >> Associate Technical Lead >> WSO2 Inc.; http://wso2.com >> email: [email protected] cell: +94 77 3791887 >> blog: http://mytecheye.blogspot.com/ >> > > > > -- > *Chanaka Sampath Cooray* > Undergraduate | Department of Computer Science and Engineering,University > of Moratuwa > Mobile: +94 71 361 4884 > E-Mail: [email protected] > Linked-In: https://lk.linkedin.com/pub/chanaka-sampath/65/221/102 > <https://lk.linkedin.com/pub/chanaka-sampath/65/221/102> > -- *Chanaka Sampath Cooray* Undergraduate | Department of Computer Science and Engineering,University of Moratuwa Mobile: +94 71 361 4884 E-Mail: [email protected] Linked-In: https://lk.linkedin.com/pub/chanaka-sampath/65/221/102 <https://lk.linkedin.com/pub/chanaka-sampath/65/221/102>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
