J
James Franklin
Hi Rob, Sylvain,
I was planning to close each connection immediately it is no longer
required. For example, when I open a form, I would open a connection,
populate the form and close the connection again. When saving an updated
record, open a connection, save the record, close connection.
I know this results in slightly slower performance, but would this not be
more efficient, bandwidth-wise, than opening a single connection and
maintaining it while the application is running? I realise there is overhead
in negotiating the connection, but at least it is only for a fraction of a
second. Is there a significant overhead in maintaining a connection even
when nothing is happening?
Once again, I really appreciate the advice you guys are giving me,
Jim
I was planning to close each connection immediately it is no longer
required. For example, when I open a form, I would open a connection,
populate the form and close the connection again. When saving an updated
record, open a connection, save the record, close connection.
I know this results in slightly slower performance, but would this not be
more efficient, bandwidth-wise, than opening a single connection and
maintaining it while the application is running? I realise there is overhead
in negotiating the connection, but at least it is only for a fraction of a
second. Is there a significant overhead in maintaining a connection even
when nothing is happening?
Once again, I really appreciate the advice you guys are giving me,
Jim