Hi, What I mean is to do a table of pros VS cons of dropping this feature. For instance, I just remember someone did a profiling of his application and reported that wicket (in his application) was slower after this feature was introduced (a pro of removing it, maybe wicket will be faster). All the work to get rid of it (a con).
On Wed, Jun 2, 2021 at 9:43 AM Martin Terra < martin.te...@koodaripalvelut.com> wrote: > ke 2. kesäk. 2021 klo 9.36 Ernesto Reinaldo Barreiro (reier...@gmail.com) > kirjoitti: > > > Hi, > > > > On Wed, Jun 2, 2021 at 9:14 AM Martin Grigorov <mgrigo...@apache.org> > > wrote: > > > > > On Tue, Jun 1, 2021 at 10:51 PM Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > > > Hi Martin, > > > > > > > > How much work do you think this will imply? > > > > > > > > > > Removing the component queueing ? > > > I am not sure. Removing should be easier than implementing it. > > > Why do you ask ? > > > > > > > It is removing + fixing back all things that were changed because of > this > > feature.I have the impression this implied a lot of minor changes. Now it > > is reverting all that and making sure everything works again. Thus I was > > just wondering if it will be worth the effort to do that just to remove > > something that is almost working in all cases. > > > > +1 > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
