On 08/07/2013 02:16 PM, Lars Doelle wrote:
> Not sure I get your scenario right.
What i want to do is to setup a TCP-server from within LibreOffice that
is able
to read and send raw data over the wire using some Basic routine processing
it in between.
You can't do that with LibreOffice BASIC, but could do it with a
LibreOffice extension written in some language that allows to spawn
additional threads.
> 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}.)
If you say above some '--accept=<parameter>' magic would already create
a silly TCP-server that passes all connections accepted to some Basic
routine
for further read and write i would definitely love to learn more about
this trick.
No, it allows external code to connect to LibreOffice via the UNO remote
protocol (URP).
Unfortunately, i didn't find any syntax or options for the
'<parameter>'. We're
using "--accept=socket,host=0,port=2002;urp;", but this implies
UNO-marshalling,
which we want to get rid of for reasons outlined in the original mail.
Ah, now I think I understand your original mail better---your problem
with incompatible Python versions means you want to replace the URP
communication between the two applications with something not using UNO.
In which case, forget what I wrote about --accept, and rather try to
create an extension as outlined above.
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.