Tag Info

New answers tagged

1

In general, you can do everything you want to in Javascript without involving a controller, except for final data validation. In other words, always assume that the client has been hacked, and act accordingly. That said, a modal following another modal seems like a marginal design. Modal dialogs are, by far, the most expensive possible UI element to the ...


0

Inheritance I have used inheritance before as a solution for passing common data to many of the same pages (user, role, event tracking/logging, profile information, and other data). This is convenient in some cases, but not always ideal. For instance, you may add profile data to the base model for pages where they can add their email address, or display ...


0

An alternative approach, which may or may not be appropriate for your situation, would be to implement a queue and have a worker thread or process which processes items in the queue. There would always be only a single instance of the worker. The worker processes requests in a FIFO order. This way you eliminate race conditions - if two users both sign up ...


1

I would go with locking and making sure that validating the enrollment is single-threaded. This is similar to any one of another similar scenarios where a potentially large number of users are attempting to secure a scarce resource: registering for class/training, booking a seat on an airplane, buying a movie theater ticket in advance for opening day of a ...


2

I've seen dynamically changing DB systems- driven by configuration where the customer adds columns "on the fly" for metadata that they want stored in addition to a few fixed columns. In all cases, you're now driving your application using configuration, and that means your queries have to be calculated at runtime - this rules out all systems that determine ...


1

I keep view models in the web project, for reason you stated, it's usually only useful to the relevant view. I'm not sure why your data access layer would reference the web project though?


0

If the POST is changing state on the server, then respond to the POST with a 303 so that the browser can GET a page describing that new state (that is, from page 1 you are directed to page 2 and the information page 2 contains was affected by the POST). History will now work correctly. If the state of page 2 is a reflection solely of the choices made on ...


0

I've worked on and continue to work on large scale api projects and I've never used the BindAttribute. I would say with this code remove it completely, it will still work and it will remove the error prone strings in the attribute. Personally and from my experiences you shouldn't pass out your data entities from an api endpoint. We use view models, but ...



Top 50 recent answers are included