Pass object from an app to another
-
I have a win app and a web app developed in .Net Framework 3.5. I want to pass an object from web to win app. I want the receiver app be notified from coming object and recive it. What are the solutions?
Best wishes
-
I have a win app and a web app developed in .Net Framework 3.5. I want to pass an object from web to win app. I want the receiver app be notified from coming object and recive it. What are the solutions?
Best wishes
Your options: 0) Write a web service that you then access from your desktop app (not kowing the specific details of the data being requested, or why it's being requested, this is the way I'd do it) 1) Write a new page on your web site that you can browse to that returns the data you want, and use the HTTPWebRequest object to browse to that web page. You can't "push" to the desktop app because web services and web sites are request-driven, meaning the data is only returned when that data is requested.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
I have a win app and a web app developed in .Net Framework 3.5. I want to pass an object from web to win app. I want the receiver app be notified from coming object and recive it. What are the solutions?
Best wishes
Please look into the Bayeux Protocol[^]. It was based on the idea of inverting the usual client request / server response paradigm. Of course the client still has to connect to the server and keep that connection open, but after that the server can push notifications/data to the client. I'm not sure if there are any client side APIs that would let you use this in a WinForm application, but you could circumvent this by using a webbrowser control inside your WinForm application. Best Regards,
—MRB
"With sufficient thrust, pigs fly just fine."
Ross Callon, The Twelve Networking Truths, RFC1925
modified on Monday, August 22, 2011 10:58 AM
-
Please look into the Bayeux Protocol[^]. It was based on the idea of inverting the usual client request / server response paradigm. Of course the client still has to connect to the server and keep that connection open, but after that the server can push notifications/data to the client. I'm not sure if there are any client side APIs that would let you use this in a WinForm application, but you could circumvent this by using a webbrowser control inside your WinForm application. Best Regards,
—MRB
"With sufficient thrust, pigs fly just fine."
Ross Callon, The Twelve Networking Truths, RFC1925
modified on Monday, August 22, 2011 10:58 AM
This is an interesting answer (hence my vote of 5)! I was 404'd on the link, but this works: http://svn.cometd.com/trunk/bayeux/bayeux.html[^] the URL just needed an "l" on the ".html"
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^] -
This is an interesting answer (hence my vote of 5)! I was 404'd on the link, but this works: http://svn.cometd.com/trunk/bayeux/bayeux.html[^] the URL just needed an "l" on the ".html"
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^]Thanks Keith. It looks as if deep linking isn't allowed. I pasted in the link from the google page and now it works. Cheers!
"With sufficient thrust, pigs fly just fine."
Ross Callon, The Twelve Networking Truths, RFC1925
