Use HTML5 pushstate

[pstoica]

Would everyone be alright with putting the JSON controllers in /api/ so we can use HTML5 pushstate instead of hashbang URLs?

[jakswa]

Do we know what browsers our audience will be using? Hopefully they, too,
know that IE is to be avoided (IE8 and below, for sure)...

On Thu, Jun 6, 2013 at 1:29 PM, Patrick Stoica notifications@github.comwrote:

Would everyone be alright with putting the JSON controllers in /api/ so we
can use HTML5 pushstate instead of hashbang URLs?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/30
.

[pstoica]

Angular provides a fallback for older browsers if you use html5mode. Only problem right now is that routes are kind of clashing.

[jakswa]

Oh, nice, I'm all for that, then. We'll just need to make sure that any
server-side URL rewriting by rails happens if needed. "Using HTML5 mode
requires URL rewriting on server side, basically you have to rewrite all
your links to entry point of your application (e.g. index.html)."
-linkhttp://docs.angularjs.org/guide/dev_guide.services.$location#htmllinkrewriting

On Thu, Jun 6, 2013 at 3:11 PM, Patrick Stoica notifications@github.comwrote:

Angular provides a fallback for older browsers if you use html5mode. Only
problem right now is that routes are kind of clashing.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/30#issuecomment-19067435
.

[pstoica]

In that case we can just set up routes in the /api/ namespace and redirect anything else to root (Devise will also be moved over to Angular, so that could also go in /api/). Seem good?

[v3n]

+1 from me.

On Jun 6, 2013, at 4:45 PM, Patrick Stoica notifications@github.com wrote:

In that case we can just set up routes in the /api/ namespace and redirect anything else to root (Devise will also be moved over to Angular, so that could also go in /api/). Seem good?

—
Reply to this email directly or view it on GitHub.

[jamesdabbs]

No longer relevant. See #84.