Hi Jelle Duives,
First question:
There are (at least) three options, depending on what you want to achieve.
(a) some implementations support pipe transports
(b) you could write your own transport implementation. It's not that hard,
for a starting point I would recommend to look for the existing transport
implementations first.
(c) If that's still not what you are looking for: Have a look at the
serialization mechanisms that come with Thrift and build an custom RPC
mechanism around that. A little more work, but not impossible.
Second question:
Have you tried using a threaded server instead of the simple server?
For a more detailed answer it could be helpful to know what language(s) you
are using, as not all features are available everywhere. Additionally, it
could be important whether or not both communication endpoints share the
same address space.
Jens
-----Ursprüngliche Nachricht-----
From: Duives, J. (Jelle)
Sent: Friday, August 2, 2013 12:06 PM
To: [email protected]
Subject: Thrift over memory
Dear thrift mailing list,
We're using thrift for a project having multiple modules on a single system.
These modules communicate over thrift and therefore we would like to send
the information over the system memory. Is that possible, and if yes, do you
maybe have a simple example for me?
Another questions is about a single-server, multiple-client connection.
Right now we are using the TSocket and TServerSocket as connection. However,
on a single system we have one server that should be reachable by two
clients. Is that possible without having to recreate the socket every time
the client calls the server?
Kind regards,
Jelle Duives
This e-mail and its contents are subject to the DISCLAIMER at
http://www.tno.nl/emaildisclaimer
