M
matthewlowrance
We have an application that uses an access database. Some of our
client have requested a Client /Server version that they can use over
their wan.
I have created a simple server that queries the database and then
turns the dataset into xml, then sends the xml across the network and
then the client turns the xml back into a dataset. This seemed like
the simplest method so the application could work client/server or
connect directly to the access database for other clients.
The only thing I'm unsure about is just generally what is the best
practice in a .net application, creating a single connection on the
client side and keeping it open for the duration of the application or
reconnecting to the server each time a new dataset would be requested
and dispose the connection objects/let them be garbage collected?
The server is multi threaded so it would work either way.
If there is a better architecture I'd would be happy to hear that as
well.
Thanks for any help,
Matt
client have requested a Client /Server version that they can use over
their wan.
I have created a simple server that queries the database and then
turns the dataset into xml, then sends the xml across the network and
then the client turns the xml back into a dataset. This seemed like
the simplest method so the application could work client/server or
connect directly to the access database for other clients.
The only thing I'm unsure about is just generally what is the best
practice in a .net application, creating a single connection on the
client side and keeping it open for the duration of the application or
reconnecting to the server each time a new dataset would be requested
and dispose the connection objects/let them be garbage collected?
The server is multi threaded so it would work either way.
If there is a better architecture I'd would be happy to hear that as
well.
Thanks for any help,
Matt