I am about to attempt to set up a system that will use one process, a non
photon app, for data processing and then periodically some of that data will
be passed to a photon app to update the user interface. I cannot afford to
have my non-photon app blocked but the photon app can be blocked momentarily
if need be. I have been looking at using a client-server approach,
non-photon app as server, however, I am relatively new to IPC and I welcome
any suggestions on how to best implement this. Thanks.
Ross Brantner
“Ross Brantner” <brantner@nrc.net> writes:
I am about to attempt to set up a system that will use one process,
a non photon app, for data processing and then periodically some of
that data will be passed to a photon app to update the user
interface. I cannot afford to have my non-photon app blocked but
the photon app can be blocked momentarily if need be. I have been
looking at using a client-server approach, non-photon app as server,
however, I am relatively new to IPC and I welcome any suggestions on
how to best implement this. Thanks.
Well, if you are willing to pay for a commercial product, we sell a
product (Cascade DataHub, nee Cascade Database) that allows your data
processing application to send to a non-blocking data server that will
then pass on the information asynchronously to your Photon
application. Neither of your processes will block, and you can have
as many client apps as you like passing data back and forth with the
data processing app.
If your data flow is sufficiently simple, you can instead use mqueue
to get data one-way from the data processing app to the Photon app.
Cheers,
Andrew
Andrew Thomas, President, Cogent Real-Time Systems Inc.
2430 Meadowpine Boulevard, Suite 105, Mississauga, Ontario, Canada L5N 6S2
Email: andrew@cogent.ca WWW: http://www.cogent.ca