New answers tagged

1

Does your DBMS care about which naming convention you use? No Do you care? You probably do, just like any other human would. Everyone has a preference. Do your colleagues care? Yes? Consult with them. Does your ORM care? You should be able to answer this one yourself. I'm not familiar with Dapper but I have experience with Entity Framework, ...


3

Your business logic should remain untouched. The Rest API is a view. The UI is a view. At most the controller should change to accommodate this change. In an ideal design the controller would have no knowledge of any views and wouldn't change at all. Rather than showing the flow of information it would have been helpful to see the directions of ...


0

It seems that you want map the joined tables to composite objects. For this task is best use already mentioned ORM framework (best with JPA specification). Mapping relations to composite objects can be done in one-round-trip in ORM. ORM using more ways to optimize data access. But you must learn quite a complex framework. Mentioned common approach with ...


1

I'm going to answer my own question after a day of research. In the end this ended up looking more towards cron jobs which support MVC web applications (which isn't exactly the same as my original question but yielded some interesting information none-the-less). Anyway, here's what I found: Q. The concept of routing all requests to one file is a little ...


-1

There are more than 1000 way except MVC some of them are similar to MVC and some totally different for example : Model-Template-View - MTV Model–view–presenter - MVP Hierarchical model–view–controller HMVC Model View ViewModel- MVVM etc


2

In the Microsoft version of MVC, you have the heavy Controller implementation instead of the heavy Model implementation that a large portion of the development community uses. The ORM should be a part of the Model layer, but a lot of Microsoft documentation has Entity Framework (which is their ORM) throughout the Controllers. In a lot of ways, it makes ...


0

The Model is everything that is not in a View or a Controller. That includes the ORM, regardless of whether it is Ruby on Rails, ASP.NET MVC or some other flavor of MVC.


0

I'm from the Java World, but things are pretty similar, so here are some hints about rights checking in my opinion. If your right is a right like "have the right to perform action X". Then you should check before routing and in the service layer. The check in the service layer is to be sure that whenever you call that service, you'll have a said check. ...


0

Authentication should happen after routing but before calling controller or its methods. At that point you know which route was requested and can check if user has privileges to perform a certain action (call controllers). This allows not only to separate concerns, but also to decide how to handle unathorized requests before they hit controllers - eg. ...


0

ASP.net has nothing to do with video streaming. Video streaming is achieved using intelligent video encoding and manifests in combination with a CDN. We use: Flowplayer with HLSJS (Javascript) CloudFront as the CDN Encoding.com API to encode videos. ASP.net on the backend to handle the business logic. Streaming is usually achieved via an HLS file ...


1

What you're seeing in the line of code <source src="@Url.Content(Model.tbl_Video.VideoPath)" type='video/mp4' /> is just ASP.NET MVC's way to insert the correct source element into a <video> tag. ASP.NET MVC has no responsibility whatsoever in the streaming process. The browser streams the video content directly. Further Reading HTML ...


1

The examples shown is correct, but Zend\Form is not exactly what you want to use in your controllers. I'm talking about Exhibit A, where it shows how much code to create, populate and style a form with two elements. It is tedious to create forms that way. To avoid turning the controller into a form factory, you need to create a factory that will create the ...



Top 50 recent answers are included