stevestreza / barista Goto Github PK

I noticed that when I attached a query to my URL, it wasn't showing up in the parameters. I tracked this down to a change in commit 4fa48b7. Instead of routing on the request.URL it routes on the request.URL.path in order to avoid the problem of JLRoutes using the host in the path.

This looks like some kind of rock and hard place. If the URL is used, the query is left alone, which is good, but the host is used, which is bad. If the URL.path is used the host is stripped off, which is good, but the query is also stripped off, which is bad.

Is JLRoutes using the host 'A Good Thing'? I notice the comment in that code says it is for some kind of backward-compatibility; maybe JLRoutes should not do it at all, or have a switch to disable it or something (which I realise is a topic to take up in the JLRoutes issues).

I'm putting this here because I don't think it is working right, but I don't know what is the right solution.

For the time being, to make it work in my app (I'm using Barista as a dev helper to dish up JSON to the iPhone app I'm developing), I have simply gone back to using URL for routing, and commented out the part of JLRoutes which uses the host name for routing.

I've followed the demos to setup a simple server but all my requests are hanging. I'm using the latest master.

http://cl.ly/image/060X0h1k1E36

For example, in the demo app, GET /layout. The server never returns a 404 nor 500. By default, shouldn't it always return a response?

It seems like it might be due to a missing spec in the podspec file.

Is there an API for WebSockets? If not, will that be added soon or are you waiting for someone else to make middleware?