[Enigmail] IPC library usage

Patrick Brunschwig patrick at mozilla-enigmail.org
Tue Feb 5 09:57:30 PST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Damiano Albani wrote:
> Hello,
> 
> On Feb 4, 2008 1:16 PM, Patrick Brunschwig <patrick at mozilla-enigmail.org
> <mailto:patrick at mozilla-enigmail.org>> wrote:
> 
> 
>     If that doesn't help then you could maybe try to replace
>     "C:\dummy.exe with C:\\windows\\system32\\cmd.exe /c dir C:\\"
> 
> 
> Nope, still the same issue... :-/
> Could I have a look at the exact JS code you used ?

ipc/tests/ipctest.js and tests/tests/ipc.js

> Mine can be seen on <http://pastebin.mozilla.org/320744>. I suppose I
> must pass an incorrect argument at some point.

Indeed I think you do :-) I imagine that you use a recent nightly build
of Enigmail -- but if you check the latest ipc tar file
(http://mozilla-enigmail.org/ipc/ipc-latest.tar.gz), you'll see that the
1st parameter has changed, it's now an nsIFile. I.e.

it should be:
var dummyFile =
Components.classes["@mozilla.org/file/local;1"].createInstance(Components.interfaces.nsILocalFile);
dummyFile.initWithPath("C:\\Dummy.exe");
dummyFile = localfile.QueryInterface(Components.interfaces.nsIFile);

pipeTransport.init(dummyFile,
                   aArguments, aArguments.length,
                   [], [].length,
                   0, "", true, true, null);


> By the way, it's far from being the first project I do where I need to
> use your excellent IPC library -- without Enigmail code itself.
> How could we/you organize to have a IPC-only component available
> somewhere for the main platforms and applications (Firefox, Thunderbird,
> SeaMonkey, Calendar, etc). Because that's a really useful piece of code,
> irreplaceable as long as the default Mozilla API doesn't integrate your
> code (supposing it's ever going to happen).
> 
> Thanks a lot for your help,

You can actually build ipc separately from Enigmail, just unpack the tar
 file to .../mozilla/extensions, and build it just like you'd build
Enigmail.

I currently don't create regularly builds of ipc. The difficulty is that
Thunderbird and SeaMonkey need to be compiled differently than Firefox,
XulRunner etc, and I just can't create 8 variants of ipc builds in
addition to the 4 variants of Enigmail that I already build.

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEVAwUBR6ijiXcOpHodsOiwAQIZFwf/WDO0pQgJyQBBH7ZWG+NvzUmPLomm6nn5
PA5DCaT6xltpb0siVni+v4JKM4PSWV0gxiXj1mPAuhORJ7GkG91h5U8PqZdDqmYW
yOsAiFo5VRyc17zWsg/lBDpeIOH60Z0/0OR8w8ssAPZHlujJkgtiKHhISIa5OmVg
uPh9zQYKkK+zJ+DjRWiITJZYizZE5Y1njY8SAPvbXMTjKqPF/ETiz6V7y6TLK8Gb
XhQcI7QzKPQe9SeAY7DBWC6peD/9coVgUlaxOuJp391hty8aD9t8CW5EmH9H3r79
aUt4yinm+YpyhKY28MFi3fEPDhDymb0d0if59p5ekJpHMhKAfj55hg==
=w1T8
-----END PGP SIGNATURE-----


More information about the Enigmail mailing list