think about SQL Ce with merging replication.
It is quite ligth concerning acually transfered data and facilitate offline
scenarios.
"Lebesgue" <(E-Mail Removed)> a écrit dans le message de news:
(E-Mail Removed)...
> If the application is not performance critical and you want to develop it
> faster, use webservices.
> There is some overhead with XML serialization and delays, but development
> process is made very simple.
> When using sockets, you get more performance, but many possible
> implementation problems you have to deal with.
>
> "Rob S" <(E-Mail Removed)> wrote in message
> news:3E2DE25B-8ED3-4FA5-A6F6-(E-Mail Removed)...
>> I have a specification to do some very simple stuff on a PDA.
>>
>> Basically, it will need to:
>>
>> (all over gprs)
>>
>> 1) Receive jobs over from our server
>> 2) Send back certain information about those jobs (ie. dates etc)
>>
>> Would you use sockets for this or web service?
>>
>> At the moment i'm using sockets and while it's OK it's a bit of a pain
>> opening the correct gprs connection and sending and receiving
>> data..etc...
>>
>> I'm thinking web services might be good because it will automatically
>> dial
>> the gprs and it avoids sockets altogether.
>>
>> Any opinions out there?
>
>