If REST is there to just get the facts, is the staleness and needing attention a fact or not?

It really depends how you intent the REST interface to be used. If you should be able to build a non-web client app using it that more or less looks just like the client app, then the login result should return that info.

I'm a little dubious about the whole concept of sharing a controller between views. Seems like all too often you are going to run into situations like this. Which is not to say controller and view shouldn't be separated! Just that the benefit of that separation is something other than reusability of the controller.

--
CollegeGear.com - more than just college gear (though, yes, we have college-branded teddy bears)

In reply to Re: Web: interactive, REST: batch? by ysth
in thread Web: interactive, REST: batch? by talexb

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.