On Thu, Apr 3, 2008 at 3:04 PM, Brian Eaton <[EMAIL PROTECTED]> wrote:
> There are currently two versions of the request content-type floating > around the Shindig java code, one in the > RemoteContentRequest.contentType variable and another in the > RemoteContentRequest.headers variable. Values can make their way into > the content type through several mechanisms, including javascript > running on the client and hardcoded values in the Shindig code. > > I'm sure there is some corollary to Murphy's Law that says that if you > have two versions of a piece of data floating around, one will be > wrong. I'd like to fix RemoteContentRequest so that there is a single > location that someone can check to see what content-type header was > specified by gadgets.io.makeRequest. Does anyone feel strongly about > where that single location should be, or should I just pick one? The current code always extracts contentType from the headers, unless they're not set. They should always be the exact same value, unless there's no Content-Type header. It's extracted at creation time and there's no way to modify it after that (or the headers). The reason why I added this method was because there are cases where you need to extract the contentType, and there's a lot of boiler plate code for doing so...no sense duplicating it. > > > Cheers, > Brian > -- ~Kevin
