Handling Content Type as we should, through HTTP Headers
In the previous postI spiked a solution to return different result types depending on a requested format. While the solution I came up with was sufficient to address the points issued on a thread at .NetArchitects, Eric Hexterhit the nail on the head with the following tweet: @pedroreys nice post on the formatter. I would consider http headers instead of routing, although that is hard to manually debug The right way to specify the types which are accepted for the response is by using the Acceptrequest-header.
Mimicking Rails formatter behavior in ASP.NET MVC
I was reading this (pt-BR) thread at the brazilian .Net mailing list – dotNetArchitects – which, at first, did not have nothing to do with Rails nor output format. But, as usual, the thread deviated from the initial subject – what is not a bad thing – and somehow got into the fact that it would be nice to have in ASP.NET, more specifically in ASP.NET MVC, a behavior similar to what Rails have by default to handle output formatters.
Alternative MBA with Seth Godin
Look this trade-off: Instead of getting a MBA, spend 6 months at the office of one of the greatest marketing authors and blogger. That’s what Seth Godinis offering. Quoting him, what he offers is: Six intense months working with a few other amazing people (and me.) It is a really awesome opportunity for one who already lives or can afford the expenses of living 6 months in NYC.
Hi everybody. This is the first post of my new blog. Some of you may be familiar with the Portuguese written blogthat I co-author with Jorge Maia. At this one I’ll be writing in English only, I hope. :) Well, as soon as I finish all the WordPress settings, I will start to post here. For you who don’t know me yet, I suggest reading the “About” section. Cheers, Pedro Reys