Asfar,
Generally speaking, I would say to avoid remoting. With how common web
services are, as well as better distributed technologies such as Windows
Communications Foundation on the horizon, you aren't going to gain much from
remoting. Remoting also doesn't provide much out of the box in terms of
authentication and authorization, so if you have a need to secure your
service (which I hope you would, given it is on the internet), then I would
avoid it.
Using web services allows you to provide a solution now, and as long as
you keep your contract the same, you can swap out the implementations on the
client or server side easily.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Asfar" <as**********@cashmgmt.comwrote in message
news:u9**************@TK2MSFTNGP05.phx.gbl...
>I would like to build a thin client application which will display data and
images from database.
The user will have a look at the data images and post it back to server.
I would like to know which will work better in this scenario. Should I use
Webservice or remoting to pump data from database to client?
Thanks,
-Asfar