C
Chris Adamson
Hi!
My company is starting a solution where we will be dealing with multiple
Pocket PC's updating a database concurrently (each one doing so once every
8 - 30 seconds).
There will be some processing done via SQL Server stored procedures to help
consolidate the data as there is some central logic done on each PDA's data.
We don't want each PDA to have to wait in order to post its data to the
database (i.e. this will be done in a dedicated separate thread if pushing
the data to the stored procedure takes too long).
My request for comments is for how you would go about implementing this
system. The work to put the data into the database will be done through a
stored procedure, so the Pocket PC's don't have to call much (or push much)
data to the database.
I was considering doing a Web Service that would call the stored procedure,
but I'm not sure how responsive it would be in a local environment with
approx 3 to 20 PDA's potentially calling the web service all at once.
I have also read briefly about .NET remoting but I don't even know if the
little Pocket PC can handle this.
Finally, I am mostly a C++ programmer (MFC) and so doing raw sockets is also
an option... but there seems to be a lot of support for higher level .NET
communication across networks (or is it mostly hype
).
I guess the biggest question is: What solution path would you take in terms
of
- development time (this is a pilot project)
- scalability
- extensibility
- simplicity
Is there enough built in goodies in .NET such that I won't have to 'reinvent
the wheel' too much?
Thanks for your time.
-Chris
My company is starting a solution where we will be dealing with multiple
Pocket PC's updating a database concurrently (each one doing so once every
8 - 30 seconds).
There will be some processing done via SQL Server stored procedures to help
consolidate the data as there is some central logic done on each PDA's data.
We don't want each PDA to have to wait in order to post its data to the
database (i.e. this will be done in a dedicated separate thread if pushing
the data to the stored procedure takes too long).
My request for comments is for how you would go about implementing this
system. The work to put the data into the database will be done through a
stored procedure, so the Pocket PC's don't have to call much (or push much)
data to the database.
I was considering doing a Web Service that would call the stored procedure,
but I'm not sure how responsive it would be in a local environment with
approx 3 to 20 PDA's potentially calling the web service all at once.
I have also read briefly about .NET remoting but I don't even know if the
little Pocket PC can handle this.
Finally, I am mostly a C++ programmer (MFC) and so doing raw sockets is also
an option... but there seems to be a lot of support for higher level .NET
communication across networks (or is it mostly hype
).I guess the biggest question is: What solution path would you take in terms
of
- development time (this is a pilot project)
- scalability
- extensibility
- simplicity
Is there enough built in goodies in .NET such that I won't have to 'reinvent
the wheel' too much?
Thanks for your time.
-Chris