 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Remoting / October 2006Romting vs Web Service in vs2005
I'd like to get some ideas of the best way to accomplish the following in vs2005: Win1 - a windows application Web1 through WebX- many website applications I'd like to talk from Web1-WebX to Win1 and also back through, at this thinking, a web service. I need Win1 to communicate to only a specific Web application at a time. I don't need the websites to talk to each other, though. For example: Web1 messages to Win1 "Name: Joe" Web2 messages to Win1 "Name: Mary" Web3 messages to Win1 "Name: Bigfoot" Win1 responds to each of these websites individually, not like a broadcast message. I think .Net Remoting might be a better way to go than a WebService, but I'm not sure. I really don't know that much about Remoting, so if someone is suggesting that, can they also point me to a good tutorial or book? Thanks, Dave OK, sorry about the typo in the subject and another tidbit: The websites are not restricted to the same machine the Win1 is on (I thought this was obvious, but I just want to be clear). > I'd like to get some ideas of the best way to accomplish the following in > vs2005: [quoted text clipped - 19 lines] > Thanks, > Dave > I'd like to get some ideas of the best way to accomplish the following > in vs2005: [quoted text clipped - 17 lines] > someone is suggesting that, can they also point me to a good tutorial > or book? What sort of messages are you passing back and forth? Will it be primarily primative data types? If they are - web services will suffice. If you need to pass complex data types (typed objects, .NET data types, etc) I would use remoting. Remoting should provide better performance than web services if you're transferring large amounts of data. Bi-directional communications should be easier with remoting as well. SC, Thanks for the quick reply. I think at this point I'll pretty much be sending a simple string. The thing is, with a web service, I don't know, if say 5 web users have instantiated the web service, how can my windows app call the web service and tell it to send info to just one of the websites? Doesn't each website instantiate the web service, and then how will the web service instantiated through the windows application even know where to route the reply messages? Or am I over-complicating things? > > I'd like to get some ideas of the best way to accomplish the following > > in vs2005: [quoted text clipped - 27 lines] > > Bi-directional communications should be easier with remoting as well. > I think at this point I'll pretty much be sending a simple string. > The thing is, with a web service, I don't know, if say 5 web users > have instantiated the web service, how can my windows app call the web > service and tell it to send info to just one of the websites? With web services, each web service is a different class - you need to pre- generate the web service proxy beforehand. Thus, with web services, you need to know the servers up front. I believe there are way to dynamically generate the web service proxy on the fly, but I have never done it before. If you need to dynamically call/register servers ... it is very easy to do in remoting. > Doesn't > each website instantiate the web service, and then how will the web > service instantiated through the windows application even know where > to route the reply messages? Or am I over-complicating things? Routing reply messages is the challenging part with web services - web services doesn't support bi-directional messaging... so you'll need 2 web services on each box - a sender and receiver. If bi-directional communications is a requirement, go with remoting or a custom solution like sockets + XML? SC: Thanks again. I guess it's Remoting for me. Any outstanding, can't miss articles or tutorials you know of? Thanks, Dave > > I think at this point I'll pretty much be sending a simple string. > > The thing is, with a web service, I don't know, if say 5 web users [quoted text clipped - 22 lines] > If bi-directional communications is a requirement, go with remoting or a > custom solution like sockets + XML? > SC: Thanks again. I guess it's Remoting for me. Any outstanding, > can't miss articles or tutorials you know of? How to do stateless bi-directional remoting in IIS: http://www.codeproject.com/csharp/persistentevents.asp How to do bi-directional remoting (non-stateless): http://www.codeproject.com/csharp/RemotingAndEvents.asp I hope that helps : ) Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.