recent posts
Recently, I re-created this blog site, yokolet’s notelets, from scratch. Still, it is made by Jekyll like it was, but now, CSS styles are defined by Tailwind CSS. This blog post is about what I did to build the website.
Ruby on Rails is famous for offering really various features which are helpful to create a web application. Among those, little known API might be the low level caching API.
The previous two blog posts introduced WebSocket and how to implement a WebSocket application on Ruby on Rails. This blog post digs deeper. It is a memo on creating a more realistic application by Action Cable.
The previous blog post, WebSocket on Rails by Action Cable, focused on WebSocket as a protocol. As in the previous post, by default, Rails app responds to WebSocket connection requests without any hassle.
In the web application domain, we hear some protocol names. Absolutely, HTTP or HTTPS is the most famous protocol that all web developers know. Although there’s a mechanism of Keep-Alive, a single request/response sequence with a single client/server is all done by HTTP.
“When you type a URL in your browser, what will happen?” If you are a web developer, you might have answered this sort of interview question once or twice. It would be a popular question to test the knowledge how the Internet works.