ipc

Passing an object from one application to another in android

由 99封情书 提交于 2019-12-07 18:06:55
问题 After lot of googeling, I could not find any way to pass a object from one application to other application.Though I know that we can pass object from one activty to other activity using Parcel but how to do this between applications? My object is this public class MyObject { private String name; public String getName() { return this.name; } public void setName(String name) { this.name=name; } } Then how to do this like we do for passing object between activities intent.putExtra("key",new

.Net 3.5, most secure way to pass string between processes

由 依然范特西╮ 提交于 2019-12-07 10:29:16
问题 I'd like to be able to pass a SecureString (a cached passphrase) to a child process in C# (.Net 3.5), but I don't know what the most secure way is to do it. If I were to convert the SecureString back to a regular string and pass it as a command-line argument, for example, then I think the value may be prone to disk paging--which would make the plaintext touch the filesystem and ruin the point of using SecureString. Can the IntPtr for the SecureString be passed instead? Could I use a named

Two way communication using Cromis IPC

由 折月煮酒 提交于 2019-12-07 10:29:13
问题 I've downloaded and had a play with the Cromis IPC components from Iztok Kacin. I've downloaded this component set to allow my windows service and GUI to communicate. However it seems that the communication is one way(apart from server responses). I can quite happily send a message from a client to a listening server, but I don't appear to be able to send a message back to the client unless it is as a response. Does anyone know if two way comms are achievable with these components or am I

How can we share the data using shared memory segment with “Object” between two managed processes?

由 こ雲淡風輕ζ 提交于 2019-12-07 09:08:28
How can I share the data between two managed processes using shared memory segments? I am using "object" inside C++/CLI code to share the data with some other part of memory in the other process. I am using following code segment. #define BUFFER_SIZE 32768 #pragma data_seg (".SHAREDMEMORY") bool _Locked = false; bool _Initialized = false; unsigned char[10000] data = NULL; #pragma data_seg() #pragma comment(linker,"/SECTION:.SHAREDMEMORY,RWS") but I need it to be: #pragma data_seg (".SHAREDMEMORY") bool _Locked = false; bool _Initialized = false; object^ _object = nullptr; #pragma data_seg()

IPC: Connect for each request or keep socket open?

由 元气小坏坏 提交于 2019-12-07 08:46:15
问题 I am planning to use sockets (local TCP) to communicate between two processes (running locally). One process will act as a server, but both processes send messages to each other asynchronously. Should I keep the socket connection open for the lifetime of the processes, or re-connect for each request? Are there any problems that may occur if I keep a local socket open? 回答1: Keep the socket open. Its the simpler option and you don't incur in the overhead of opening a new socket (from the client

How to choose the “Key” for inter-processes communication in Linux?

由 女生的网名这么多〃 提交于 2019-12-07 08:14:14
问题 Good Day... I am doing a homework which states that I have 5 processes; a server and the rest are clients. Each process is supposed to be sparked from a different executable . I am going to implement a two-way message passing solution, but the question is not about message passing per se. Is there an elegant way to communicate the key between those different executables. i.e. when I call the following function: int msgget(key_t key, int msgflg); How are other processes supposed to know the

Recommended way of sharing an object between C# processes

由 和自甴很熟 提交于 2019-12-07 08:12:34
问题 I have read numerous different things about IPC between 2 C# applications and their pros and cons, but don't feel like I have reached a satisfactory answer yet for my use case. I have an object that already exists that will change frequently (I am trying to attach my tool to a game and use it to debug elements created with the tool). As a result, I don't beleive serialisation is appropriate as I would essentially be serialising/de-serialsing the object 60 times a second for no good reason. As

Qt portable IPC: only QSharedMemory?

由 前提是你 提交于 2019-12-07 07:57:20
问题 I'm looking for suggestions about choosing a portable way to achieve local IPC in a robust way, since i'm new to C++ and would like to avoid common pitfalls of fiddling with shared memory and locks; therefore I was thinking about message-passing style ipc. I was planning to use qt for other reasons anyway, thus i took a peek to Qt ipc options. if i understand correctly qt doesn't offer a completely portable message-passing ipc feature. it can use d-bus, but using it on windows would be a

Some source that implements named pipes communication btw service applications or help about it

由 会有一股神秘感。 提交于 2019-12-07 07:54:27
I'm implementing my own named pipe Client/Server class, but I'm getting too much troubles and no much information about on internet. I already found a lot of implementation with pipes but with vlc application but I'm working with service applications. I accept hints about how to work with pipes too. My actual problem is: While server the app just receive one message from the client, after this my server can't use PeekNamedPipe() any more. My error message that I get from GetLastError is "there is a process on other end of the pipe", but.... I don't know what to solve do with this. If I close

Share CGAL's geometry between processes in C++

由 房东的猫 提交于 2019-12-07 07:13:10
问题 I'm looking for the fastest way to send CGAL's geometry between processes (C++). Lets assume, that we have 2 processes - A and B. Process A is generating geometry and process B is displaying it. I want to connect them in the fastest awailable way. The geometry is of CGALs Polyhedron type. I know I can use shared memory, but then I've got some problems: When I want to copy geometry from process A to shared memory I can use streaming Polyhedron to/from OFF format, but I’m not interested in it,
订阅 ipc