> > Initial discussion was to run this tasks at midnight, because all the > substitution start at beginning of a day.
Ok, now I understand what you meant initially. > Since we are moving to time-stamp based approach, we will not required to > calculate this for all users; but calculate for some users (if there are > transitive substitutes.), when a substitution of an user starts. Agreed. > Who will trigger this event. ? It is a task, that will be scheduled when the substitution is created. What I meant is we can '*think*' about that as a timed *event *since it's per user. It don't matter, really. To summarize: +1 for the task approach where only one user is handled in the task. On Mon, Jun 6, 2016 at 1:17 PM, Hasitha Aravinda <[email protected]> wrote: > Hi Manu, > > On Mon, Jun 6, 2016 at 10:12 PM, Manuranga Perera <[email protected]> wrote: > >> Let's say, engine hasn't received any new task creation requests >>> for >>> this particular user during T1-T5. Then engine will not able to >>> reassign above X tasks back to user B during this time period. But user B >>> should able to >>> perform >>> above task after T1. >>> This is why we can't >>> use >>> event driven pattern here. >> >> Let's take an example. Say we use event driven pattern here and we have >>> substitution from user A to user B which >>> is >>> defined at T0, starts at T1 and end at T10. Currently User A has x >>> number of in-progress tasks. >> >> >> Yes, we do need tasks to re-assign the user, but this doesn't mean we >> need a separate task to calculate for all users. >> > > Initial discussion was to run this tasks at midnight, because all the > substitution start at beginning of a day. So we had to calculate this for > all users. > > Since we are moving to time-stamp based approach, we will not required to > calculate this for all users; but calculate for some users (if there are > transitive substitutes.), when a substitution of an user starts. > > > >> We can consider this task as the end of substitution event. >> > > W > ho will trigger this event. ? > > Thanks, > Hasitha. > > >> >> -- >> With regards, >> *Manu*ranga Perera. >> >> phone : 071 7 70 20 50 >> mail : [email protected] >> > > > > -- > -- > Hasitha Aravinda, > Associate Technical Lead, > WSO2 Inc. > Email: [email protected] > Mobile : +94 718 210 200 > -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
