in reply to Web: interactive, REST: batch?

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)

Replies are listed 'Best First'.
Re^2: Web: interactive, REST: batch?
by talexb (Chancellor) on Dec 21, 2007 at 02:48 UTC
      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.

    Mmm.

    It seemed to make sense to me to have the application share everything, and just output different stuff based on which template (web or REST) that it was using. But you raise a very good point -- now I'll (presumably) have to change the behaviour of the application based on which mode I'm in, and that's something I was trying to handle completely using templates.

    Alex / talexb / Toronto

    "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

[reply]
[reply]

In Section Meditations