Even then, we have votes with which we can steer how things should be done. We have project meetings in which we discuss what to do and when. The possibility of input is there.
And contrary to popular belief, I, at least, do listen and concider other suggestions. Some suggestions are simply not feasible, at least not now.
The scanpage object had to leave the core (it cntained too many SCAN specific stuff), and a simple solution had to be made to bridge the gap.
We cannot remove HttpServletRequest from the core at this point, no matter how hard you want that, because it is currently used on too many places. Once the function framework is in use, we can migrate to that and get rid of it, but we're not there yet.
In the mean time, we need something that is at least less ugly than scanpage. PageContext was a bad name, so I will rename it to PageInfo, but other than that it fulfills it's (temporary) function.
The moving of code to applications is not random. I specified what I think should move and where, and why. Most people agree.
The Tools package is the only fluke, and people have pointed out they don't like it and I am going along with that opinion (have to find a solution for the individual classes though).
I also agreed that a messaging interface in the core may be useful, though I am in doubt whether it is actually required.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
