2 ms·

How exactly would you parse parameters in a web application framework differently?

• sanderjd 14y ago
  As always in software, there are lots of options. Here are two: 1. Provide the action with the raw request body as a string. It is then solely responsible for any and all parsing. 2. Provide the action with the raw request body as a string, but provide standard parsing classes that the action can use depending on what they are specifically doing. Both of those solutions would make the parsing code less abstract than the Rails solution, with different trade-offs. I believe this entire thread started because I claimed that Rails has chosen to be further toward the abstraction side of the scale. I can't tell if you really think I am wrong about that, or if you merely think that the choice Rails has made is the right one. If it's the latter, I agree with you, and never claimed otherwise. But it is a choice, and it has trade-offs.