Connection Manager-like component

P

Patrick Hayes

Hi

I am looking for a component that provides connections (GPRS/WiFi/...) from
applications on a PDA (PocketPC) to a server running webservices.

I have found www.BroadBeam.com and they have some interesting products, but
is there anyone else on the market? Or would I/we (the company i work for)
be better off with a DIY solution?

- patrick
 
P

Paul G. Tobey [eMVP]

The OS itself 'provides connections'. What, exactly, are you expecting from
this component?

Paul T.
 
P

Patrick Hayes

The OS itself 'provides connections'. What, exactly, are you expecting
from
this component?

We need a component that can keep the application always connected, when
moving from Cradle to WLAN to GPRS and back, handle prioritized trafic (some
packets only gets send when WLAN or cradle is provided, or after a timeout),
preffered networks, moving in and out of coverage. stuf like that.

Patrick Hayes
 
P

Paul G. Tobey [eMVP]

Well, the OS itself handles prioritizing the traffic, so it would be
worthwhile to make sure that what's already there for that isn't what you
need. It will depend on the usage pattern (long term TCP connection and
frequent loss of high-speed network signal, or short term connection and
occasional change of networks).

I suspect that this is going to be too specific to your application to be
generally available. Here's a little scenario that might show why:

You're connected, via TCP, to a server with which you are exchanging data.
Suddenly, you pass out of range or into a dead spot for 802.11. It will
take some time for this to be detected, so there's a delay built in. If the
TCP connection decides that it's dropped, then your socket will indicate
that fact and you'll have to establish a connection another way. Let's say
that it's GPRS. The connection is established and you connect to the server
with TCP again. Do you now change what goes to the server? Only the
application knows the meaning of what it's sending. A few moments later,
you pass back into an area of 802.11 coverage. You can't just change how
the TCP packets are sent to the server. Your connection was established
from the GPRS adapter. To change, you have to break that connection,
reestablish the TCP connection with 802.11 and proceed from there. Knowing
which packets go and when which networks are connected is another
you're-the-only-one-who-knows thing.

Maybe someone else has heard of some component that does this sort of thing,
but I haven't. I think that this is something you'll have to build
yourself. As I said, OpenNETCF can help you know when new networks show up
and old ones go away. The OS will choose the 'lowest-cost' method of
establishing a connection, so you may be able to use that fact to avoid
having to bind to a specific adapter when making connections. Your code
code wrap that connection control with something through which the
application could send various types of 'packets' (not network packets, but
packets that mean something to you), and the wrapper could decide whether to
send them now or not.

Paul T.
 
S

Steve Maillet \(eMVP\)

Seamless roaming of this sort does not exist. Microsoft and others are
working towards solutions for that to integrate that into the core OS but
it's a HUGE problem, requiring support on the client device, the backend
server and just about everything else in between.
 
P

Patrick Hayes

Looks like i have to tell my boss that it is going to be a DIY solution
again...
We have solutions like this built in C/C++ running on Linux/Windows,
switching between radio, gsm, gprs and lan. But it would probably have been
cheaper to buy something readymade, than doing a complete rewrite/port for
pocketpc+dotnet.

anyway, thanks both of you.

- patrick
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top