New Nugets (0.9.3.723) this morning

[Jeremy D. Miller]

Guys,

I made a push this morning with a couple fixes for problems introduced in the last couple pull requests.

* Conneg:  What to do if the request accepts "*/*"?  A recent pull request changed the behavior to make the conneg output ignore a request that accepts "*/*" and assume that a following behavior will handle it.  This leads to scenarios where no output happens and fubu just goes on its merry way while you pull out all of your hair.  I changed the behavior of the ConnegInputBehavior to check if there is a following behavior.  If there is one, it continues assuming that the next behavior would handle it correctly.  If there is no following behavior, the ConnegInputBehavior will just select the first media writer that it knows about and does its thing.  

   * Permanent fix:  My thinking is that we use a system level policy that pulls the view rendering with an accept of "text/html" into the ConnegOutputBehavior so the ConnegOutputBehavior can accurately control everything.  It turns out that Josh, Roy, and I need the "view profile / conditional view rendering" thing for mobile views soon-ish, so I get daytime work hours to make all of this happen.

* The HttpContext crap.  The changes to how we resolve HttpContext for the async rippled some other problems that both the Dovetail guys and I ran into.  I changed the DebugReport to eliminate the direct usage of HttpContext/HttpRequestBase (makes it a lot more OWIN friendly too) and changed how AggregateDictionary was registered to avoid the problems (maybe, hopefully).  Please let me know if you see any issues with this one.

Thanks,
 

Jeremy D. Miller
The Shade Tree Developer
jeremy...@yahoo.com

[Chad Myers]

Cool, thanks Jeremy!

For everyone else: It still helps to make sure to set the "datatype" on your AJAX requests (i.e. $.post(type, url, data, successCallback, dataType)) because otherwise jQuery will just send "*/*" which is non-optimal.

Also, there was some bogus code in StructureMapFubuMvcRegistry that loaded the AspNetAggregateDictionary that was causing problems. Jeremy removed this.   The AspNetAggregateDictionary is still getting properly loaded in the AspNetServiceArguments if you're in an ASP.NET context (vs. an OWIN context). 

-Chad

--
You received this message because you are subscribed to the Google Groups "FubuMVC Development Group" group.
To post to this group, send email to fubumv...@googlegroups.com.
To unsubscribe from this group, send email to fubumvc-deve...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fubumvc-devel?hl=en.