One slightly better way to get more eyes on an issue is to file it in the JSF spec project on www.java.net. Then it'll go off to the full "dev" list, and will be officially tracked.
That said, it's rather unlikely that anything will happen for JSF 1.2. At this point, it'd have to be a rather critical issue (and, like I said, without numbers, it's hard to prove that it is critical.) Cheers, Adam On 12/11/05, Simon Kitching <[EMAIL PROTECTED]> wrote: > > Adam Winer wrote: > > Fair enough, but as with most performance questions. > > actual numbers are of the essence. I've had thoroughly > > brilliant (so I thought) insights into how to make code faster > > that, after measuring, didn't do a darn thing. And since > > you're adding memory allocations (which, at higher > > server loads, will decrease performance), you'd want to > > see a convincing improvement. > > I'd be happy to *not* have to do this hack. If the JSF spec would > provide some method to set an attribute without getting the old value > returned that would be far better (hint, hint). I've sent a request > through to the [EMAIL PROTECTED] address on 7-dec to change the > API so this hack isn't necessary but not got any response so far. > > Cheers, > > Simon >
