the name 'parseKey' has existed for almost a year, back when I didn't really understand what I wanted. It's was used everywhere to capture the parse result json, but "key" in it's name was misleading, when compared to other functions that actually took a key name, as opposed to a json response with a key in it's dictionary. So to enhance understanding, this name really had to change. I use ...Result in other places to name the captured json response from an h2o thing, so I think this makes it more consistent. Now the runRFOnly() style api in h2o_cmd, takes parseResult as input, rather as a key, which is debatable, but I think can be useful (for passing extra stuff without changing the main api)..also it's nice and simple for feeding parse results simply into the next function.