Do they belong to you? Claim these comments.
Dan Kubb
Is this you? Claim Profile »
7 months ago
in [ANN] alter-ego 1.0.0 Released on Virtuous Code
This looks pretty nice. I was curious tho, have you looked at Mixology? I was thinking that the state blocks could setup anonymous modules, and instead of the handle blocks you could use normal methods. Each module would correspond to a specific state and get mixed into the object as part of each state transition.
1 reply
avdi
It's an approach I've considered, and I may move towards it, although I'm pretty sure I want to stay compatible with explicit state classes. One of the items on the TODO list, however, is being able to define ordinary ordinary methods in state { } blocks instead of using #handle.
1 year ago
in The last of the Merb 0.5.x line on Gweezlebur
Mike, a good resource to check merb against for its HTTP compliance is the following flow chart:
http://thoughtpad.net/alan-dean/http-headers-st...
It gives alot of information about how requests should be handled, and what status codes to return in certain situations. Its missing a few things, like returning 422 Unprocessable Entity when a PUT or POST request body is well formed, but contains invalid information (Fielding commented in rest-discuss this was the best status to return in this case); otherwise its probably one of the best resources aside from RFC 2616.
http://thoughtpad.net/alan-dean/http-headers-st...
It gives alot of information about how requests should be handled, and what status codes to return in certain situations. Its missing a few things, like returning 422 Unprocessable Entity when a PUT or POST request body is well formed, but contains invalid information (Fielding commented in rest-discuss this was the best status to return in this case); otherwise its probably one of the best resources aside from RFC 2616.