About Services Clients Contact

About Node.js

"You Lied Again": Rahul Gandhi On PM Modi's "Made In Amethi" Swipe

தமிழில் படிக்கবাংলায় পড়ুনहिंदी में पढ़ें

Lok Sabha Elections 2019: PM Modi said Amethi would have a "new identity" and would be known by the AK-203 Kalashnikov rifles that would be made there.

All India | Reported by Alok Pandey, Edited by Deepshikha Ghosh | Updated: March 04, 2019 11:08 IST

by Taboola

Sponsored Links

Sponsored

Going Bald? This ’10 Days’ Ayurvedic Hair Oil from Kerala can Help You! (10 Days Hair Oil)

Why investing at Dwarka Expressway is better than rest of Gurgaon? (Sobha Limited, Gurgaon)

 SHARE

EMAIL

PRINT

36COMMENTS

'You Lied Again': Rahul Gandhi On PM Modi's 'Made In Amethi' Swipe

Lok Sabha Elections 2019: Congress president Rahul Gandhi represents Amethi in the Lok Sabha.


NEW DELHI: 

A day after Prime Minister Narendra Modi visited Rahul Gandhi's constituency Amethi in Uttar Pradesh to launch a manufacturing unit for AK-203 rifles and targeted him at a rally there, the Congress president posted a tweet accused him of "lying by force of habit".

"I laid the foundation stone of the ordnance factory in Amethi in 2010. For many years it has produced small arms. Yesterday you went to Amethi and as is your habit, you lied again. Have you no shame," the Congress president tweeted in Hindi this morning.

Shortly afterwards came a retort from Union Minister Smriti Irani, who has been a frequent visitor to Amethi since she contested the 2014 election from the constituency against Rahul Gandhi and lost, but by a lesser margin than the Congress expected. "Yo

 

This is in contrast to today's more common concurrency model where OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. Furthermore, users of Node are free from worries of dead-locking the process, since there are no locks. Almost no function in Node directly performs I/O, so the process never blocks. Because nothing blocks, scalable systems are very reasonable to develop in Node.

If some of this language is unfamiliar, there is a full article on Blocking vs Non-Blocking.


Node is similar in design to, and influenced by, systems like Ruby's Event Machine or Python's Twisted. Node takes the event model a bit further. It presents an event loop as a runtime construct instead of as a library. In other systems there is always a blocking call to start the event-loop. Typically behavior is defined through callbacks at the beginning of a script and at the end starts a server through a blocking call like EventMachine::run(). In Node there is no such start-the-event-loop call. Node simply enters the event loop after executing the input script. Node exits the event loop when there are no more callbacks to perform. This behavior is like browser JavaScript — the event loop is hidden from the user.

HTTP is a first class citizen in Node, designed with streaming and low latency in mind. This makes Node well suited for the foundation of a web library or framework.

Just because Node is designed without threads, doesn't mean you cannot take advantage of multiple cores in your environment. Child processes can be spawned by using our child_process.fork() API, and are designed to be easy to communicate with. Built upon that same interface is the cluster module, which allows you to share sockets between processes to enable load balancing over your cores.



0

Related Articles