help with Firefox extension in multiple windows

I'm writing a Firefox extension that creates a socket server which will output the active tab's URL when a client makes a connection to it. I have the following code in my javascript file:

var serverSocket;

function startServer()
{
    var listener =
    {
        onSocketAccepted : function(socket, transport)
        {
            try {
                var outputString = gBrowser.currentURI.spec + "\n";
                var stream = transport.openOutputStream(0,0,0);
                stream.write(outputString,outputString.length);
               开发者_高级运维 stream.close();
            } catch(ex2){ dump("::"+ex2); }
        },

        onStopListening : function(socket, status){}
    };

    try {
        serverSocket = Components.classes["@mozilla.org/network/server-socket;1"]
        .createInstance(Components.interfaces.nsIServerSocket);

        serverSocket.init(7055,true,-1);
        serverSocket.asyncListen(listener);
   } catch(ex){ dump(ex); }

   document.getElementById("status").value = "Started";
}



function stopServer ()
{
    if (serverSocket) 
    serverSocket.close();
}

window.addEventListener("load", function() { startServer(); }, false);
window.addEventListener("unload", function() { stopServer(); }, false);

As it is, it works for multiple tabs in a single window. If I open multiple windows, it ignores the additional windows. I think it is creating a server socket for each window, but since they are using the same port, the additional sockets fail to initialize. I need it to create a server socket when the browser launches and continue running when I close the windows (Mac OS X). As it is, when I close a window but Firefox remains running, the socket closes and I have to restart firefox to get it up an running. How do I go about that?

Firefox extension overlays bind to window objects. One way around this is to create an XPCOM component or find one that someone else already created to allow you to build functionality without binding it to the window objects.

Of course, section #2 below on Observer Notifications may be helpful as well.

Possible workaround: #1

Instead of calling "startServer()" each time a window is opened, you could have a flag called windowCount that you could increment each time you open a new window. If windowCount is greater than 0, don't call startServer().

As windows close, you could decrement the count. Once it hits 0, stop the server.

Here is information from the Mozilla forums on this problem: http://forums.mozillazine.org/viewtopic.php?f=19&t=2030279

Possible workaround #2:

With that said, I've also found documentation for Observer Notifications, which may be helpful as there is a section on Application Startup and Shutdown: https://developer.mozilla.org/en/Observer_Notifications

UPDATE:

Here are some resources on creating XPCOM components in JavaScript and in C++:

• https://developer.mozilla.org/en/how_to_build_an_xpcom_component_in_javascript
• http://www.codeproject.com/KB/miscctrl/XPCOM_Creation.aspx
• https://developer.mozilla.org/en/creating_xpcom_components

You probably want to:

1. Move your code into a JavaScript component
2. Register your component as a profile-after-change observer
3. Whenever someone makes a connection to your socket, find the active window and return its URL.

Use something like

var wm = Components.classes["@mozilla.org/appshell/window-mediator;1"]
                   .getService(Components.interfaces.nsIWindowMediator);
var win = wm.getMostRecentWindow("navigator:browser");
var spec = win ? win.getBrowser().currentURI.spec : "";
var outputString = spec + "\n";

etc.