request.env["PATH_INFO"]
Unfortunately, that's now coming back empty.
As it turns out, I 'solved' this problem twice in two different ways. A different part of my code uses
action.node.r(action.path, request.params)
and that's still mostly working. But I don't know why I did that, or where I got it from. I asked the installed documentation to tell me more about 'action.' It isn't aware of that method at all. Just 'action_missing'. Google sent me (not surprisingly) to the "Journey" book. It give me a list of action's methods. "Path" is not one of the 'members' listed. "Node", according to the example, probably contains a Controller. But the Controller class doesn't have an "r" method described in the docs either.
grep grep grep read source grep grep read source
Ah, I've found it. There's a whole different block of documentation under Innate. "r" is an alias for "route." "Route," rather amusingly, has a bunch of examples that all use "r" instead of "route".
It ends with
"@return [URI] to the location"
which I'm guessing is supposed to mean
[route] returns a URI to the new location
The presence of the commercial-at sign is baffling.
> Since Innate is based on Rack, can't you use the methods listed at
> http://rack.rubyforge.org/doc/classes/Rack/Request.html for doing this
> kind of things?
Hmm. I have no idea.
So Innate builds on/uses Rack, and Ramaze builds on/uses Innate.
I think what I need to do is re-run RDoc, feeding it all the files from all three systems so I can all the applicable modules and methods to appear in the same place at the same time.
Are there any other components involved that I would want to include?