Developers Buddy

REST supports the following HTTP methods: GET: It requests a resource at the request URL. It should not contain a request body as it will be discarded. May be it can be cached locally or on the server. It can have request headers. POST: It submits information to the service for processing; it should typically return the modified or new resource. It can have both request body and request headers. PUT: At the request URL it update the resource. It can have both request body and request headers. DELETE: At the request URL it removes the resource. It can have both request body and request headers. OPTIONS: It indicates which techniques are supported. HEAD: It returns meta information about the request URL.

Yeah, It looks like a weird. Did you try anytime this command? NPM INSTALL is not a valid command. All the NPM commands should be in lower case. 

There’s no big difference between the regular DOM and the virtual DOM. It’s better to think of the virtual DOM as React’s local and simplified copy of the HTML DOM. It allows React to do its computations within this abstract world and skip the real DOM operations, often slow and browser-specific. Real DOM operations are really really expensive. The Virtual DOM is an abstraction of the HTML DOM. It is lightweight and detached from the browser-specific implementation details.  One thing you should remember that the DOM itself was already an abstraction. So, Virtual DOM is an abstraction of an abstraction. :)

The amount of JavaScript tools is steadily increasing, turning the selection of appropriate technology into a challenge. But why developers are most interested in React js among those libraries. Nowadays all the web applications are in SPAs. It means the DOM trees are huge nowadays, in turn we need to modify the DOM tree incessantly and a lot. This is a real performance and development pain. Consider a DOM made of thousands of divs. We have lots of methods that handle events - clicks, submits. What can do by the library like jQuery? jQuery will find every node interested on an event and update it if necessary It has two problems: It’s hard to manage and it’s inefficient. The solution to problem 1 is declarativeness. Instead of low-level techniques like traversing the DOM tree manually, you simple declare how a component should look like. But this doesn’t solve the performance issue. This is exactly where the Virtual DOM comes into action. First of all - the Virtual DOM was not invented...

Single-Page Applications (SPA) are Web apps that load a single HTML page and dynamically update that page as the user interacts with the app. SPAs use Javascript libraries and HTML5 to create fluid and responsive Web apps, without constant page reloads. However, this means much of the work happens on the client side, in JavaScript.

 Machine.config file contains settings that apply to an entire computer. Machine.config contains configuration settings for machine-wide assembly binding, built-in remoting channels and ASP.NET. Machine.config would be the primary configuration lookup file. I mean, the configuration system first looks in the machine configuration file for the appSettings element and other configuration sections. It then looks in the application configuration file. So, How can we use Machine.config efficiently? To keep the machine configuration file manageable, it is best to put these settings in the application configuration file. However, putting the settings in the machine configuration file can make your system more maintainable. For example, if you have a third-party component that both your client and server application uses, it is easier to put the settings for that component in one place. In this case, the machine configuration file is the appropriate place for the settings, so you don't hav...

Prism offering two injection containers named Unity and MEF. Both the containers have their own capabilities. Before choosing the container decide your environment needs. Some of the capabilities provided by both ( Unity & MEF ) containers include the following: Both register types with the container. Both register instances with the container. Both imperatively create instances of registered types. Both inject instances of registered types into constructors. Both inject instances of registered types into properties. Both have declarative attributes for marking types and dependencies that need to be managed. Both resolve dependencies in an object graph. Unity provides several capabilities that MEF does not: Unity resolves concrete types without registration. Unity resolves open generics. Unity uses interception to capture calls to objects and add additional functionality to the target object. MEF provides several capabilities that Unity does not: MEF discovers assemblies in a dir...