Tag Info

Hot answers tagged

2

You're almost there... Putting the REST between the view and the controller would be the right choice. That means that your view, i.e. a javascript code, will send REST calls to your server, which process those calls in the appropriate controller (then the models and etc.). In addition this controller would be responsible for the response back to the ...


1

First rule of thumb - never start over if you can avoid it. That's a Joel Spolsky rule of software development. So that's automatically a strike against re-writing your app in HTML5. Fortunately, you really only have to re-write the client. You can update the server app incrementally, but you don't need to replace it wholesale. However, moving from ...


1

Don't reinvent the wheel. .NET Framework already has logging that you can easily use in your application. The logging framework will handle the multithreading for you (and TraceSource is thread-safe according the documentation). Under the hood, when the log file cannot be written (which is quite rare, since TraceSource uses a global lock internally, and ...



Only top voted, non community-wiki answers of a minimum length are eligible