A Web API and Web Page all in one == recipe for failure for 90% of the time.
1
1
@tourismgeek A web page is a web api, it just happens to return a representation that has HTML payload ;-)
2
@darrel_miller @tourismgeek However IMO generating views on server is not recommended. View is a client-concern #CSDS
1
@aliostad Not surprisingly, I think it depends. For the applications I build, I like views to be a server concern.
1
@darrel_miller and you are not alone. @stilkov thinks the same. But this violates REST's client-server constraint.
7
@aliostad @darrel_miller I disagree. You haven't explained why you think so yet.
1
@stilkov b/c view is a client concern. REST client-server: separation of concerns. #verbatim /cc @darrel_miller
1
@aliostad I understand your point now. I still disagree: (the right kind of) HTML is not view code, and HTML+CSS+JS offers a very nice SoC
2
@stilkov difference here is that yoy send back a composed resource. We say server renderee view. "render" gives it away.
3
Replying to @aliostad
@aliostad Whatever, though, I'm quite convinced @fielding would disagree with the "server-side HTML breaks REST" view

Dec 14, 2012 路 7:56 AM UTC