Cache results of parsing URI parameters

[szeiger]

Menu.param allows you to define a parser and an encoder for a URI parameter. The parser is a good place to retrieve an item from a database and automatically get a 404 if it is not found, but the parsing is performed multiple times per request and the result is not cached. As a workaround, you can manually thread the result through a RequestVar. It would be nice to have a caching Menu.param available in Lift out of the box.

[indrajitr]

Updating tickets (#919, #938, #950, #956, #976, #980, #982, #999, #1008, #1024, #1025, #1032, #1034, #1051)

[indrajitr]

Updating tickets (#950, #956, #976, #980, #982, #999, #1008, #1053, #1078, #1092, #1097)

Pushed pending tickets to 2.4-M5

[indrajitr]

Updating tickets (#956, #976, #980, #982, #1008, #1053, #1078, #1092, #1097, #1128)

[indrajitr]

Updating tickets (#906, #950, #956, #960, #976, #980, #982, #997, #999, #1008, #1053, #1078, #1090, #1092, #1097, #1128, #1134, #1155, #1168)

[github-importer]

Imported from Assembla: http://www.assembla.com/spaces/liftweb/tickets/982

[Shadowfiend]

This actually came up again on the list the other day—is the idea here that we would stick the results of the parse in a TransientRequestVar?