On Mon, Aug 10, 2009 at 2:02 PM, James Strachan<james.strac...@gmail.com> wrote: > 2009/8/10 Roman Kalukiewicz <roman.kalukiew...@gmail.com>: >> Just few general comments on the topic here: >> >> 1) My impression is that we are trying to solve problem that doesn't >> exist. No one would expect that getting "foo" header should retrieve >> what was put under "FOO" key. If we want to have guarantee that it >> works properly people should use constants for it. It is the way that >> Java world solves those problems >> 2) If we create CaseInsenstiveMap class we will fail to obey Map >> contract. Let's take a look at Map.containsKey() method's contract in >> javadoc. And my impression is that we want to treat headers as a Map, >> don't we? >> >> In protocols that has case-insensitive headers (like http) I believe >> component should take care of it by (for example) setting headers >> using lowercase keys only (for example) and it should be clearly >> stated in component's documentation, as in Camel components are >> responsible for handling protocol-specific features. > > I think camel should preserve what its given by default though. e.g. > passing requests from HTTP or email into Camel shouldn't rename > headers IMHO >
And this is exactly what it does now. If a header is stored as "Foo" then it stays that way. However you can also look it up using "foo". > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
