Changes between Initial Version and Version 1 of Ticket #1844


Ignore:
Timestamp:
07/02/11 23:37:11 (5 years ago)
Author:
simon
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1844 – Description

    initial v1  
    11Right now, if the user opens Standalone after opening Firefox 3.6, we are hanging Standalone startup and hanging Firefox 3.6 on shutdown, because Firefox 3.6 can receive a releaseLock command, but it can't send a lockReleased command. We can ignore the releaseLock command, but Standalone will still hang expecting a lockReleased command. At the very least, we want Standalone to display an error message. Our options are: 
    22 
    3 1) Have standalone wait a fixed amount of time for a response after requesting that the DB lock be released before erroring out and closing (or, alternatively, before trying to open the DB again) 
    4 2) Implement the connector switching messages with the almost entirely undocumented version of js-ctypes that came with Firefox 3.6 
    5 3) Find a way to get the version of the running Firefox process using ctypes from within Standalone 
    6 4) Some kind of trick involving passing the ZoteroIPC command line option with nsIProcess 
    7 5) Drop support for Firefox 3.6 on Windows entirely 
     31. Have standalone wait a fixed amount of time for a response after requesting that the DB lock be released before erroring out and closing (or, alternatively, before trying to open the DB again) 
     42. Implement the connector switching messages with the almost entirely undocumented version of js-ctypes that came with Firefox 3.6 
     53. Find a way to get the version of the running Firefox process using ctypes from within Standalone 
     64. Some kind of trick involving passing the ZoteroIPC command line option with nsIProcess 
     75. Drop support for Firefox 3.6 on Windows entirely 
     8 
    89I think I am going to implement option 1, since it seems like a good idea anyway. If this isn't sufficient, I'll revisit this.