routing

I am creating a site with CakePHP, and I need to set some URLs for static pages, which are handled by the pages controller. Basically I want to have two different types of static pages, with the URLS mysyte.com/page which should map to app/views/pages/page.ctp and mysite.com/special/page which should map to app/views/pages/special-page.ctp . Note that in the first case page can be 'special' as well. I am a bit lost with the routing I have to set up for this situation. I have tried to use the two routes Router::connect( '/special/:mypage', array('controller' => 'pages', 'action' => 'display'),

I'd like to have a routing rule that accepted part of my domain name as a parameter. For example: {name}.mydomain.com/photos/{id} Is this even possible? I have had a similar issue in using asp.net mvc, but with using the whole domain instead of just the subdomain. What we used was a custom route constraint to determine which controller to go to (domain determined controller on our project). Then in the controller we used the normal asp.net request.url properties to take an action. This may or may not help depending on your exact requirements. Parsa It wouldn't be possible since the {name}

I'm developing an android application that would locate the user(assuming that the user is on the road) and the app will create the shortest route for the user to take to be able to go to the users chosen destination. Locating the user isn't the question since there's an API for that here: http://www.vogella.com/articles/AndroidLocationAPI/article.html so here's the catch. The roads ,intersections and their distances can be mapped or declared via variables in the code but my problem is that the GPS APIs i found so far would only return a longitude and latitude and not the road names or the

I'm coming from the Asp.net MVC world where route constraints are really useful. I'm currently developing an Angular JS SPA that incorporates client side routing. I would also like to add parameter constraints to my client-side routes as in: $.routeProvider.when("/post/:id/:name?") where I'd like to constrain my :id parameter to only be valid when these are numbers. I haven't found anything similar in Angular Docs (which are horrible to say the least). Can it be done? And maybe also parameter defaults? There's no built-in way to set route constraints, but you can do it pretty easily yourself

I'm using Express.js (3.0) to develop a Node web app; I'd like to have clean URLs for both user profiles: domain.com/username as well as for pages each user creates and shares: domain.com/username/pagename I really prefer the clean URLs to using something like domain.com/profile/username or domain.com/pages/username/pagename . The current route configuration for our development is bootstrapped like so: app.get('/', content.home); app.get('/about', content.about); app.get('/signup', users.signup); app.get('/login', users.login); app.get('/:user', users.profile); app.get('/:user/:userpage',

I have a category model and I'm routing it using the default scaffolding of resources :categories . I'm wondering if there's a way to change the paths from /category/:id to /category/:name . I added: match "/categories/:name" => "categories#show" above the resources line in routes.rb and changed the show action in the controller to do: @category = Category.find_by_name(params[:name]) it works, but the 'magic paths' such as link_to some_category still use the :id format. Is there a way to do this? If this is a bad idea (due to some possible way in which rails works internally), is there another

I am looking into setting database routing up for a new website I plan to create. I have been looking at the following tutorial with regards to utilising friendlyUrls from a database: http://www.asp.net/web-forms/tutorials/aspnet-45/getting-started-with-aspnet-45-web-forms/url-routing However, I would like to use the same route structure for multiple entities. Meaning: mysite.com/{PlayerName} goes to player.aspx mysite.com/{TeamName} goes to team.aspx … and so on … Could somebody point in the right direction of achieving this with asp.net. Is it possible using the built in routing engine, or