Skip to main content

Posts

Showing posts from 2020

Exploring Node.js Internals

I found a great article explaining Node JS internals, must read : https://www.smashingmagazine.com/2020/04/nodejs-internals/ Some other articles : Introduction to Node.js Being an official website, Node.dev explains what Node.js is, as well as its package managers, and lists web frameworks built on top of it. “ JavaScript & Node.js ”,  The Node Beginner Book This book by  Manuel Kiessling  does a fantastic job of explaining Node.js, after warning that JavaScript in the browser is not the same as the one in Node.js, even though both are written in the same language. Beginning Node.js This beginner book goes beyond an explanation of the runtime. It teaches about packages and streams and creating a web server with the Express framework. LibUV This is the official documentation of the supporting C++ code of the Node.js runtime. V8 This is the official documentation of the JavaScript engine that makes it possible to write Node.js with JavaScript.

Hibernate Object Conversations

Session methods to use for object conversations Save() A new instance being attached to the session. An insert will be scheduled. Update() Call Update to make a transient object persistent again. It will force a SQL update on the transient object. This is because Hibernate does not know whether the object is dirty or not and to be safe by default schedules an update. This method will throw an exception, if the entity is already registered with the session. - NonUniqueObjectException is thrown. saveOrUpdate() Either a save or an update will be called based on whether the identifier exists or not. No identifier - save is called, else update is called. Or for a better understanding, if the object is transient, then a save is called, if the object is persistent, then an update is called. Reattaching an unmodified instance - If you know for sure that an object is not modified and you just want to make it persistent again - Session.lock(item, LockMode.No

A Generic class – And why is it confusing

Go to start of metadata Generics came into java from Java 5 and has changed the way we use Collections. You now find people using and building generic classes more and more. For those who don’t know what generics is, please read the below link: http://docs.oracle.com/javase/tutorial/java/generics/index.html My gripe with generics is not with generics itself, but the convention of using placeholders as single letters like this: public class HashMap<K,V> implements Map<K,V>{} With collections, since we have been using these classes before generics came in we know that K represents the key and V represents the value. Now imagine you have class such as below: public abstract class SwingWorker<T, V> implements RunnableFuture<T> {} Now without having a look at the gory innards of Swin