Re: Cross Application Communication

Nupur wrote:
> Two major different scenarios: parallel and serial. When both application
> running at the same time - one of them is our application , we need to
> establish a connection (e.g. socket base solution, or even a file base
> solution) communicate between them. For serial method, one application
> (usually the other third party application) will launch our application with
> passing parameter.
sockets will work (see socket() in winsock), as will memory mapped files (see CreateFile/CreateFileMapping), these will be good for larger datasets, for smaller ones you could use message queues (see CreateMsgQueue).
Passing parameters will work (ShellExecuteEx(), as would storing the data in the registery(RegOpenKeyEx()), in the filesystem (CreateFile()), or in a database (CeCreateDatabaseEx2()).

> Also our application must be able to share the records (database) with other
> 3rd party application. Can we need to standardize with other third party
> application on the format of the data. What are ways that we can provide such
> interapplication communication ?
See above. you can use the same methods, just document the formats you expect/output data in.

If you want you app always running you could write a service, and communicate with it (ServiceIoControl())

Riki

--
ThemeChanger and AbstractStart for Smartphone :
http://www.IfIHadADollarForEveryTimeSomeoneSaidThatIWouldHaveMyOwnWebiste.com/

As practiced by computer science, the study of programming is an unholy mixture of mathematics, literary criticism, and folklore. -- B. A. Sheil, 1981
.

Loading