On Wed, Jan 26, 2011 at 1:19 AM, Ryan Riley <[email protected]>wrote:
> On Wed, Jan 26, 2011 at 12:45 AM, Erick Thompson <[email protected] > > wrote: > >> Ron, >> >> I was having this discussion today, and wasn't able to express the >> distinction between the two models very well. I think you are right in >> calling one a client (JS) server (WCF style service). But what would >> you call the other model? >> >> Thanks, >> Erick >> > > Resource-oriented is one way to say it. The mapping from MVC looks > something like this: > > M -> Resource > V -> Representation (could be any of HTML, XML, JSON, etc.) > C -> Route/Handler, meaning a single URI for a given resource, > differentiating by means of HTTP verb and Accept headers. The Handler aspect > would handle generating responses for the given verb. > > That's perhaps more REST than resource-oriented, but REST is the ideal. > > Or you could just call it SOA and serve up any sort of half-breed web > service. ;) > > Ryan > > That also means that you have separate C's for single vs. collections of resources. Ryan -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
