More and more convinced that SPAs and REST do not mix well together.
4
1
2
@szymonpobiega I disagree. Which is why we came up with ROCA (roca-style.org)
2
@stilkov Because they make hypermedia-based flows difficult by forcing static routing in client side code.
1
@szymonpobiega Make no mistake, I hate SPAs. But I believe they can be part of a RESTful app if they use a hypermedia format such as HAL.
2
@stilkov you can build SPAs to request hypermedia-rich responses, parse (optionally render) the data/controls. rinse/repeat. @szymonpobiega
1
1
@mamund I fully agree. @SzymonPobiega
1
@stilkov yeah, that reply should have been directed to @SzymonPobiega w/ you as cc. your roca-style.org covers this already, right?
1
Replying to @mamund
@mamund @SzymonPobiega That’s what it’s supposed to do, yes.

Jun 4, 2014 · 7:20 PM UTC

2
Replying to @stilkov
@stilkov @mamund would love to see an SPA framework use link relations instead of URLs for routers.
1
@stephen_mizell @mamund Why not skip the SPA idea altogether and use the most supported, documented, supported hypermedia format (HTML)?
2
1
more replies
Replying to @stilkov
@stilkov +1 @SzymonPobiega
2
@mamund @stilkov The problem I have is when doing SPA UI (SL replacement), frmwks make it hard to use the UI to guide the API design
1
more replies