Last post Mar 05, 2009 03:28 AM by juankoshy
Mar 01, 2009 02:58 AM|saqib_dotnet|LINK
I m trying to write a application for handhelds / pc that will communicate to a central server over the Internet.
The clients will send a message and server acknowledges the message. Thats all.
Does any one know / any examples how do we do it?
Mar 02, 2009 07:51 AM|e_kreda|LINK
The best approach will be to publish a WebService on the server, and for the client (PDA) side to implement the WebService to send the server the message.
Mar 02, 2009 11:16 AM|saqib_dotnet|LINK
Can we use Socket communication ?
Why do you suggest for Webservice?
Mar 03, 2009 03:44 AM|e_kreda|LINK
Yes it's possible to use Soket communication, .netcf support it.
But Soket communication is harder to implement, Using Webservice is the most strait forward approach.
Mar 04, 2009 06:34 AM|juankoshy|LINK
There are many approches which you can do for this particular case...
Compared to Socket Programming WCF and Web service are easy.
Let me know if u have any further queries.
Please mark the post as answer, if it helped u....
Mar 04, 2009 10:28 AM|saqib_dotnet|LINK
Thanks Juan for detail answer.
I also would like to push data from server to Clients (HH), so the communication would be both ways.
Basically this application is like to send new orders to workers and then receive changes / updates on them.
I would choose one of first 2 options.
So would you further detail on how they are different from each other and which one will work for me in long run since I want to do 2 way communication?
Mar 04, 2009 11:10 PM|juankoshy|LINK
WCF "web services" are part of a much broader spectrum of remote communication enabled through WCF. You will get a much higher degree of flexibility and portability doing things in WCF than through traditional ASMX because WCF is designed, from the ground
up, to summarize all of the different distributed programming infrastructures offered by MS. An endpoint in WCF can be communicated with just as easily over SOAP/XML as it can over TCP/binary and to change this medium is simply a configuration file mod. In
theory this reduces the amount of new code needed when porting or changing
business needs, targets, etc.
ASMX is older than WCF, and anything ASMX can do so can WCF (and more). Basically you can see WCF as trying to logically group together all the different ways of getting two apps to communicate in the world of MS; ASMX was just one of these many ways and so
is now grouped under the WCF umbrella of capabilities.
For more information check this MSDN link
In your case it is better to go for WCF.......
Mark as answer if the post helped u....
Mar 04, 2009 11:39 PM|saqib_dotnet|LINK
Can you find me any sample code that does the similar thing what I m after?
Mar 05, 2009 03:28 AM|juankoshy|LINK
oops.... I dont have much of an idea of ur requirements.....
these links can provide you with some samples...
Please go through the samples and create ur WCF web service for ur requirement.
Mark the post as answer if it helped u.