share information between applications

[Elliot]

Is there any good idea to share information between two applications(not in
the same solution) which written by me provided no SQL is used?

 

[Arved Sandstrom]

Is there any good idea to share information between two applications(not
in the same solution) which written by me provided no SQL is used?

Initial question I'd have is, what is the nature of the information? Is it
basically a shared resource? That is, a store of common data that is
persistent, and where the applications that access the common data have no
knowledge of each other?

Or do the two applications actually have to communicate? Are we speaking
then more of messages or services? Is there a conversation between the two
applications? Is one application providing data to the other? These are all
useful questions.

AHS

 

[Elliot]

Arved,
Thanks for your attention. Those text information just like what related to
a student:
ID Firstname Lastname Gender Address
1
2
3
.....
One application(a) record those information which shared to another
application(b), once b got them, they are cleared.

 

[clintonG]

XML files are used extensively for this purpose.

Arved,
Thanks for your attention. Those text information just like what related
to a student:
ID Firstname Lastname Gender Address
1
2
3
....
One application(a) record those information which shared to another
application(b), once b got them, they are cleared.

 

[Elliot]

But I do not want the content of information to be disclosed to anyone while
encryption and decryption(I do not like) are not used.

 

[Michael Justin]

Is there any good idea to share information between two applications(not
in the same solution) which written by me provided no SQL is used?

Amnong many other options (WCF, Named Pipes, Sockets) there are solutions
available which provide something called "Message-oriented middleware":

http://en.wikipedia.org/wiki/Message-oriented_middleware

For example there is the ActiveMQ Open Source message broker. Client
libraries which allow to send messages, including objects, to a message
queue, are available for .NET (and many other platforms & languages).

Hope this helps

 

[Elliot]

It helps and it is worthing a consideration.
Thanks for your idea, Michael.

 

[Arne Vajhøj]

Is there any good idea to share information between two applications(not
in the same solution) which written by me provided no SQL is used?

Do you want to share information between two running apps or
persist information used by the apps ?

Running: remoting, plain sockets, shared memory.

Persist: reconsider your no SQL constraint - a database is
the best solution.

Arne

 

[Arne Vajhøj]

XML files are used extensively for this purpose.

I would only recommend XML files for readonly usage.

Two much problem to handle multiple updates.

Arne

 

[Elliot]

Maybe XML is the most easy way.

I would only recommend XML files for readonly usage.

Two much problem to handle multiple updates.

Arne

 

[Elliot]

Just 2 running applications.
Those three are more difficult to handle structured information than XML, do
you agree?

 

[Michael Justin]

Persist: reconsider your no SQL constraint - a database is
the best solution.

afaik there is no SQL statement who looks like

INSERT INTO [other application memory] ... ;-)


I mean, polling a database table for new information every n
milliseconds will not always the best solution - think about a news
ticker type application with hundreds of clients.

Of course a database might be working in the background, as a back up
storage, but message exchange by SELECT statements could be very
inefficient.


Michael