对Express / Node.js使用favicon中间件有什么优势？

Question

I want to add a favicon to my website (written in JavaScript with Node.JS & Express). Resources on the internet point towards using the favicon-serve middleware. The Express generator also includes this middleware.

At the moment I'm serving static files with the following line of code.

app.use(express.static('./public'));

So I dropped favicon.ico in the /public folder and the favicon works like it should (without using the favicon-serve middleware).

So my question is: why would one want to use the favicon-middleware? Why not just put it in a public folder with other static resources (.css / .png / ...)?

EDIT: I'm getting some downvotes, sorry if this is too much of a "RTM"-question, but as a beginner (in JavaScript / Node.js) it's easy to get lost in the external modules. It's hard to find resources for Node.js that aren't "install this module, learn to use this module, done" - as a beginner I often want know how someone would solve a problem without another external module, even if you end up using the module anyway.

Answer 1

This is answered by the documentation for the module :

• User agents request favicon.ico frequently and indiscriminately, so you may wish to exclude these requests from your logs by using this middleware before your logger middleware.
• This module caches the icon in memory to improve performance by skipping disk access.
• This module provides an ETag based on the contents of the icon, rather than file system properties.
• This module will serve with the most compatible Content-Type.