> Is there a reason for the constant HN state change? Yes, and it's a good one. The idea is that, because an HTTP transaction is stateless, the HN server has

> Is there a reason for the constant HN state change? Yes, and it's a good one. The idea is that, because an HTTP transaction is stateless, the HN server has to maintain a database of active connections and their context, based on the visitor's IP and/or a cookie. But the database requires both storage and processor time, so if a transaction goes dormant, after a set time interval it's purged. The alternative is to extend the timeout interval, but this means the database must be made larger, and grows more or less linearly with the timeout interval -- ten times more time, ten times more storage. It's simple economics.