Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On 07/30/2013 12:48 PM, Lars Doelle wrote:
in an application, LibreOffice is used coupled with another application,
both controlling each other. Currently, the transport is asymmetric, i.e.
incoming RPCs to LibreOffice are received using UNO while outgoing are
over TCP using com.sun.star.connection.Connector. The asymmetry is only
because we were not able to get com.sun.star.connection.Acceptor going
in a way that allows to edit a document while waiting for an incoming
connection, i.e. event-driven.

Now the other (proprietary) application has an embedded python interpreter
which is compiled with UCS-2 while the system-python (under RedHat) uses
UCS-4, so importing 'uno.py' from LibreOffice does work anymore but
produces wrong strings. This happened when moving the platform from
Windows to Linux.


Seeking a solution, i write to ask for help to this mail-list. Two
solutions appear to be possible (in order of preference):

1) Use com.sun.star.connection.Acceptor to create a TCP-server within
    LibreOffice. Our problem is how to make this event-driven. Is is
    this possible at all?

Not sure I get your scenario right. If you want the LibreOffice (soffice) process to accept incoming connections, just start it with an --accept=... command line argument. (The resulting css.connection.Acceptor is running in its own thread then, to not block anything else while waiting for connections, see desktop/source/offacc/acceptor.{hxx,cxx}.)

Stephan

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.