Gianugo Rabellino wrote: > Hunsberger, Peter wrote: > > > > > It seems you've conceptually described the 80% of the > solution that is > > easy: the wrapper just has to accumulate each addition in a map or > > similar. The interesting part (the 20% that takes 80% of > the time) is > > walking these results... Does the spec have a BNF for the Vary > > header? If so, you know that -- in theory -- it is possible > to build a > > state machine or some other grammar handler that can walk the map > > (even if it has to sort it into an intermediate tree). > > This of course is possible. My question is if there should be a more > generic and intelligent proxying of HttpServletResponse's > set|addHeader() calls in the abstracted Environment. The > "Vary:" header > would be just one of the use cases. >
Umm, yes that seems a reasonable question. You've got me, but again, conceptually at least, it's sort of the same thing: now you've got a map of maps, one for each header type and you've got to make sense of them all in combination. Any bet's that the BNF for the overall representation isn't well formed (eg; allows loops)? [I can just see it now, you'll need an expert system just to assemble the headers...]Surely there are other projects (Apache, Tomcat?) that have the same issue? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
