Add a rust implementation.

[RoPP]

No description provided.

[moredip]

Thanks for the contribution. Unfortunately it seems to be failing the specs at the moment: http://www.todobackend.com/specs/index.html?https://todo-backend-rustful.herokuapp.com.

[RoPP]

That's strange, it looks ok for me :

[moredip]

Interesting. Maybe this is only failing in certain browsers. I'm using Chrome and when I run the tests the server returns "null" as the body for the todos that are created. Even trying to retrieve them via curl still results in a null body:

⋙ curl -vv http://todo-backend-rustful.herokuapp.com/18
* Hostname was NOT found in DNS cache
*   Trying 79.125.111.225...
* Connected to todo-backend-rustful.herokuapp.com (127.0.0.1) port 80 (#0)
> GET /18 HTTP/1.1
> User-Agent: curl/7.37.1
> Host: todo-backend-rustful.herokuapp.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Connection: keep-alive
< Content-Type: application/json; charset=utf-8
< Date: Sun, 09 Aug 2015 14:37:23 GMT
* Server rustful is not blacklisted
< Server: rustful
< Access-Control-Allow-Headers: content-type
< Access-Control-Allow-Methods: DELETE, OPTIONS, PATCH, GET
< Access-Control-Allow-Origin: *
< Content-Length: 4
< Via: 1.1 vegur
<
* Connection #0 to host todo-backend-rustful.herokuapp.com left intact
null

I'm wondering whether the POST used by Chrome to create these todos is somehow different from the one used by Firefox, and that's causing your implementation to create the todos differently. Here's what Chrome is posting to create the todos during tests:

POST / HTTP/1.1
Host: todo-backend-rustful.herokuapp.com
Connection: keep-alive
Content-Length: 19
Accept: text/plain, */*; q=0.01
Origin: http://www.todobackend.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.125 Safari/537.36
Content-Type: application/json
Referer: http://www.todobackend.com/specs/index.html?https://todo-backend-rustful.herokuapp.com
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.8

{"title":"my todo"}

What's really weird is if I try to reproduce this by using what Chrome claims is the same request but exported as a curl command then everything works as expected:

⋙ curl 'https://todo-backend-rustful.herokuapp.com/' -H 'Origin: http://www.todobackend.com' -H 'Accept-Encoding: gzip, deflate' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.125 Safari/537.36' -H 'Content-Type: application/json' -H 'Accept: text/plain, */*; q=0.01' -H 'Referer: http://www.todobackend.com/specs/index.html?https://todo-backend-rustful.herokuapp.com' -H 'Connection: keep-alive' --data-binary '{"title":"my todo"}' --compressed
{"title":"my todo","completed":false,"order":0,"url":"http://todo-backend-rustful.herokuapp.com/28"}
phodgson@applepie: ~/git  
⋙ curl http://todo-backend-rustful.herokuapp.com/28
{"title":"my todo","completed":false,"order":0,"url":"http://todo-backend-rustful.herokuapp.com/28"}

I think I will need your help to figure out what's your implementation sees as different between what Chrome is sending and what curl is sending.

[moredip]

Actually, when I subsequently ask Chrome to replay the same POST that created a null TODO it now succeeds! I'm now thinking perhaps your implementation has some sort of concurrency issue or race condition or something which shows up when the browser is firing off a large number of requests during the test run. Sound possible?

[Ogeon]

Quite possible. The number of threads doesn't seem to be set, so there may be some congestion if the number of available CPU cores/threads are too low. This is a problem that is caused by the use of a thread pool in Hyper and it has been reported in hyperium/hyper#368.

I implemented the Todo example in a quite naive way, so I'm not surprised if there are some other problems lurking around, that I didn't think about.

[liamsi]

For me the implementation only works if (google) Chrome is started with a --disable-web-security flag (Version 45.0.2421.0 dev (64-bit)).
Without that I get an "XMLHttpRequest cannot load http://todo-backend-rustful.herokuapp.com/18. The request was redirected to 'https://todo-backend-rustful.herokuapp.com/18', which is disallowed for cross-origin requests that require preflight." error in the console.

[Ogeon]

That's odd... There should not be a redirect, as far as I know, unless the actual list of allowed HTTP methods would count as it.

[Ogeon]

Upgrading to Rustful 0.5 should make the congestion less of a problem. It has a mechanism that closes connections if the thread pool is about to become too occupied. It's not a solution, but a temporary measure until async IO is implemented.

[RoPP]

Rustful 0.5 upgrade done! The heroku app is up to date too.

[moredip]

Tests look good now. Thanks for the contribution!