Click here to Skip to main content
15,909,325 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hallo dear all,

I am having a project that require me to make it more robust and reliable. The project can be thought as a client-server application, each side is found at a different network places. Having this, the user must not feel or know about a connection failure even if it happened. In other words, the application has to be able to work in off-line mode. My manager suggested me to operate on MSMQ API, before I go further is there any alternative to this one?

Thanks a lot
Posted
Comments
SASS_Shooter 31-May-12 12:23pm    
Listen to your supervisor.

You could roll your own solution but that will get rather large. Basically, you would include a local database file that would cache your data. You would then synchronize the changes when you get back online. However, that is much more involved than you want unless you really want offline data access. Unless you really need to do that, go with MSMQ.
 
Share this answer
 
I would say that MSMQ, either directly or through WCF is the right solution. When I was at Microsoft we went directly with MSMQ and did not bother with WCF. If you do not think that you will want to use other communication such as web, just use MSMQ: Programming MSMQ in .NET - Part 1[^]
 
Share this answer
 
Comments
Yonathan1111 1-Jun-12 10:12am    
Many thanks for all of you.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900