It doesn't make sense to cache the ViewModel
ViewModel + View = HTML. So if your view model hasn't changed then the HTML hasn't changed. You can just return the cached page.
Cache the models, because they will be reused over multiple page requests to produce different results.
I would say that the domain object has no relation to the persistence model you use in your application.
It's true that some of the web frameworks (like Rails for instance) would assume that every domain-level object could be persisted. But it's has nothing to do with the underlying principles of DDD. DDD in general defines the concept of Repository that is ...
If you are streaming your result it is likely you are using chunked encoding. This just means that there is no Content-Length in the HTTP header, instead there are "frames" (chunks) that are submitted to the client.
There is unfortunately no way to indicate a proper error when you already started streaming the content of the response.
Checkout the list of HTTP status code.
Specifically 206 and 416 - The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
just include ERROR ERROR ERROR at the ...
But why is [one-way data binding] necessary, if you can just send and receive data using the URIs exposed by the controller?
It can be necessary if you need to provide live updates in your view of data that is modified by other sources.
For example, you are building an application to track how many available emergency-care beds are available in a particular ...
The MVC patterns contains three things:
C - Controller - Which accepts the HTTP request
M - Model - Which the controller uses to pass data to the view
V - View - HTML that is rendered for the end user
There's nothing in there for business logic, data access, authentication, or many other things.
So the answer is NO it is not a complete pattern, unless ...
Is MVC a perfectly good architectural pattern for an entire application, or is it just meant to be used as the presentation layer of a layered architecture?
MVC is only concerned with the user-interaction part of an application and it is a perfectly good architectural pattern for an entire application.
The MVC pattern contains 3 parts: The Controller, which ...
MVC and CQRS are apples and hand grenades. MVC is about routing user actions from a view and returning data. CQRS is a data access pattern to avoid side effects in queries and provide a simple scaling solution. Part of the problem is that model is probably one of the most used words in patterns and not all of them are mutually exclusive.
MVC and CQRS can be ...