Re: overhead using remoting vs. TCPIP listener
- From: "<ctacke/>" <ctacke[at]opennetcf[dot]com>
- Date: Mon, 17 Sep 2007 09:03:49 -0500
Since the Compact Framework has no support for remoting the question is
somewhat academic. If you're wanting to minimize byte transferral your best
bet is probably a UDP connection and compressed data.
--
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com
"Kai Fransson" <KaiFransson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4CDB5249-18F2-4E8C-B648-8BC0406C82C0@xxxxxxxxxxxxxxxx
Hello!
I'm developing an application for mobile devices (using Windows mobile or
CE) that communicate with a server using GPRS. The cost for using GPRS is
cost/byte sent/received. Therefore I need to minimize bytes sent/received.
The mobile unit will periodically (every third minute or so) send some
data
to the server (not a lot - we're talking appr. 200 bytes). Communication
between mobile unit and server is stateless - so a single communication
will
consist of
1. Create connection
2. Pass data to server (or possible fetch data)
3. Terminate connection
My question is if the mobile application were to use .NET Remoting for
this
communication - would the overhead (counted in bytes) be too big? Would it
be
better to create my own Socket communication over TCP/IP?
Thank you in advance
Kai
.
- Follow-Ups:
- Re: overhead using remoting vs. TCPIP listener
- From: Kai Fransson
- Re: overhead using remoting vs. TCPIP listener
- Prev by Date: why can not parse asp?
- Next by Date: Re: overhead using remoting vs. TCPIP listener
- Previous by thread: why can not parse asp?
- Next by thread: Re: overhead using remoting vs. TCPIP listener
- Index(es):
Relevant Pages
|