A Controller would look like this:
Language: Scala
class MyController extends Controller{
mount("blog/", new BlogController)
mount(GET, "comment/$id"){
val c = fetchComment(params("id"))
new Answer(c)
}
}
The first "mount" registers a sub-controller with the name "blog/". The second "mount" registers an action listening to HTTP GET and the path "comment/$id". I think "mount" is a good name to register a controller. But should the method to add an action share the same name?
The method could also be named "mountAction" or "add" ... Furthermore the name can indicate the HTTP method to listen to. What of these method names do you like best?
Language: Scala
mount(GET, "path/$id" ...
mountAction(GET, "path/$id" ...
mountGetAction("path/$id" ...
onGet("path/$id" ...
handleGet("path/$id" ...
handle(GET, "path/$id" ...
add(GET, "path/$id" ...
addAction(GET, "path/$id" ...
addGetAction("path/$id" ...
Other ideas?
Each action closure should get a request object which could be passed explicitly
Language: Scala
methodName("path", (request) => {
val result = doIt(request)
new Answer(result)
})
.. or implicitely
Language: Scala
methodName("path"){
val result = doIt(request)
new Answer(result)
})
The first approach makes obvious what is happening. The advantage of implicit passing is the more concise code. What do you like better?
My ideas expanded:
Language: Scala
mount(GET, "path/$id", (request) => {
...
})
mountAction(GET, "path/$id", (request) => {
...
})
mountGetAction("path/$id", (request) => {
...
})
onGet("path/$id", (request) => {
...
})
handleGet("path/$id", (request) => {
...
})
handleGet("path/$id"){
...
}
handle(GET, "path/$id"){
...
}
add(GET, "path/$id", (request) => {
...
})
addAction(GET, "path/$id", (request) => {
...
})
addGetAction("path/$id", (request) => {
...
})
mount(GET, "path/$id"){
...
}
mountAction(GET, "path/$id"){
...
}
mountGetAction("path/$id"){
...
}
onGet("path/$id"){
...
}
add(GET, "path/$id"){
...
}
addAction(GET, "path/$id"){
...
}
addGetAction("path/$id"){
...
}
What is your favourite?]]>