Disabling browserchannels in derbyjs

Question

I found that even static pages (like error.js) in derby.js have an active connection with server. Maybe it makes sence for development (to have live updates for pages) but does it good for production? For example my main page is static but it keeps an active connection but I don't need in live update of this page (it changes monthly) and it is most visited page. And my question could (and should) I disable this active connection (browserchannel I guess) for static pages?

UPD :I think the active connection(I see progress indicator in firebug) is only when I go from a dynamic page to a static one.

Answer 1

If you use static api for generating pages, there should not be any js and live connection on these pages, just html and css. Here is example of such static error page. Probably you do something wrong.