Hi Stephan,
Thanks for the tip - that solved it.
The symbol __dso_handle__ was undefined.
I was using ld to link the shared lib.
Switching to g++ for linking solved the undefined symbol issue.
I think I understand the thread issue as well.
The UNO IPC slow is probably my
On 01/26/2013 12:01 AM, Rai, Neeraj wrote:
I have an extension that is communicating with a a standalone shared lib
running via uno exe. I start a background thread in scalc and use
osl::socket (client/server) to pass data.
In general, I would not recommend to create an own communication
] - libreoffice 4.0 - waiting on multiple sockets
On 01/26/2013 12:01 AM, Rai, Neeraj wrote:
I have an extension that is communicating with a a standalone shared lib
running via uno exe. I start a background thread in scalc and use
osl::socket (client/server) to pass data.
In general, I would
On 01/28/2013 04:04 PM, Rai, Neeraj wrote:
I had tried interprocess communication before and found it to be slow (12 sec
vs 14ms).
Somewhere in the docs, there was a mention that it has latency of 2ms.
However, if you can point me to samples or provide other advise that make it as
fast as
Thanks
Neeraj
-Original Message-
From: Stephan Bergmann [mailto:sberg...@redhat.com]
Sent: Monday, January 28, 2013 11:43 AM
To: Rai, Neeraj [ICG-MKTS]
Cc: 'libreoffice@lists.freedesktop.org'
Subject: Re: [libreoffice-dev] - libreoffice 4.0 - waiting on multiple sockets
On 01/28/2013 04
On 01/28/2013 07:39 PM, Rai, Neeraj wrote:
Hi Stephan,
I misspoke on Q2. It wasn't compilation error but a register error
CannotRegisterImplementationException:loading component library failed:.
I am not sure how to debug this as same code with osl::socket registers. Do I
need to link with
