This document discusses the Tornado web server framework. It provides an overview of Tornado, including that it is a non-blocking and scalable web server that was used by FriendFeed and is now open-sourced by Facebook. It describes Tornado's architecture, which uses an IOLoop and callbacks instead of threads to remain asynchronous and non-blocking. An example "Hello World" application in Tornado is also provided. Performance comparisons show Tornado outperforming other frameworks like Node.js and Twisted.
This document provides an overview of building a real-life application in Node.js. It discusses selecting a database like MongoDB, using Express for routing and templating, and Mongoose for modeling and interacting with the database. Key components covered include setting up routing, views, and static assets in Express, performing CRUD operations in MongoDB via Mongoose, and using templating engines like Jade or EJS. The overall goal is to build a basic content management system to demonstrate integrating these technologies.
The document discusses using the Tornado web framework to develop RESTful APIs. It provides examples of implementing RESTful APIs in Tornado, including handling HTTP verbs, returning JSON/JSONP responses, handling exceptions, scraping web pages to monitor server status, and notifying subscribers via push notifications when status changes. Other topics mentioned include internationalization, cron jobs, and related resources for Tornado and RESTful APIs.
This document summarizes and compares Ruby HTTP client libraries. It discusses the sync and async APIs of 16 libraries including Net::HTTP, HTTPClient, and Faraday. It covers their compatibility, supported features like keep-alive connections, and performance based on benchmarks. The document recommends libraries based on priorities like speed, HTML handling, API clients, and SSL support. It encourages readers to check the detailed feature matrix and report any errors found.
Droidcon Berlin 2021 - With coroutines being the de facto way of exposing async work and streams of changes for Kotlin on Android, developers are obviously attempting to use the same approaches when moving their code to Multiplatform. But due to the way the memory model differs between JVM and Kotlin Native, it can be a painful experience. In this talk, we will take a deep dive into the Coroutine API for Kotlin Multiplatform. You will learn how to expose your API with Coroutines while working with the Kotlin Native memory model instead of against it, and avoid the dragons along the way.
This document introduces Tornado Web and AsyncMongo for asynchronous access to MongoDB from Tornado applications. It discusses evented I/O web servers and the C10k problem. It provides an overview of Tornado Web and demonstrates basic usage. It introduces AsyncMongo for asynchronous MongoDB access from Tornado. It demonstrates how to fetch, insert, update and delete data from MongoDB using AsyncMongo with examples.
The document discusses Node.js and asynchronous I/O. It explains that Node.js is an asynchronous event-driven JavaScript runtime that uses a single-threaded model with non-blocking I/O to handle high volumes of simultaneous connections efficiently. It also discusses how Node.js handles asynchronous operations using an event loop and callback functions instead of blocking operations.
A WebSockets HOW-TO using Scala and Play!Framework. Links to example repositories and other resources. Created for the AmsterdamScala meetup.
This talk was given at the Dutch PHP Conference 2011 and details the use of Comet (aka reverse ajax or ajax push) technologies and the importance of websockets and server-sent events. More information is available at http://joind.in/3237.
This talk was held at the Vert.x Meetup Amsterdam on 30-07-2014. The subject is on how to get a Vert.X cluster running in Docker containers running on CoreOS without any manual configuration.