Handler name should not be used as URL path as well

[cheungpat]

The solution described here was not implemented. However, the problem is resolved by wrapping all the request data in a JSON object, which is also a solution for the described problem.

(original issue description follows)

---

There is a problem with the way the handler are registered on both the plugin side and the server side: the URL path of the handler is also the name of the handler.

This pose a problem with the http transport in which the name of the handler will appear in the URL of the plugin call request. For example,

@handler('/hello/world')  # http plugin request with use `/handler/hello/world`
def handler(request):
    return "OK"

Having slash in handler names caused the http router in the plugin side to have problem matching requests.

To solve this problem, the plugin should generate a name for the handler and pass path information to the server:

# before
{
  "name": "/hello/world",
  "methods": ["POST"],
  "key_required": True
}
# after
{
  "name": "generated_handler_name",    // request become `/handler/generated_handler_name`
  "path": "/hello/world",
  "methods": ["POST"],
  "key_required": True
}

skygear-server should use path when registering the handler with http router. To be backward compatible, skygear-server should use name key if path does not exist.

[cheungpat]

After some offline discussion, we will not implement what is described here. We will accomplish the same thing by putting the name of the handler in a JSON-wrapped request body.