what is .NET remoting?

we are trying to write an application which interacts with Financial Market data services (real time) . and I wondering if we ever need .NET remoting ....

thanks
nath

Great article here: http://www.informit.com/isapi/produc...tent/index.asp

Thanks for the article interesting read.

My knowledge of remoting and webservices isn't that broad at the moment. Could someone give me a brief overview of the advantages/disadvantages of using one over the other?

Remoting and WebService are a bit different. Remoting is a method of 'sharing' or using an object across ApplicationDomains. WebServices are typically more about a functionality then an complex object. Remoting objects typically do or can maintain state between calls, Webservices do not.

An example use of a webservice would be methods that are used but not necessarily related to each other other than subject. Things like GetRecentAccountingData, AddErrorToLog, things you just call once and forget about.

Remoting might be a user object that you might want to share the same instance of with multiple applications with events, or a factory object that resides on a server and accesses the servers local data but responds and in the client application, more complex objects that you typcially don't just call but work with.

This is not always true just an attempt at an few examples.

Thanks Edneeis,

Those examples sure helped. Basically webservices are stateless, and remoting is not. (ontop of being able to share object references)

are there good books to learn .NET remoting programming with vb.net?

thanks
nath

There is a really great book on remoting called, 'Advanced Remoting in VB.NET' by Ingo Rammer. Don't let the Advanced part fool you it covers everything from basics to very advanced. The author is great too I've seen him answer questions on newsgroups and is site can be informative as well.

http://www.amazon.com/exec/obidos/tg...books&n=507846