|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
|
|
#1
January 5th, 2004, 06:02 AM
|
|||
|
|||
|
Why use ODBC when you can do it through Socket programming?
Hi,
ODBC, as we know is used to connect to remote Databases. It is also a fact that the task that ODBC does, can be done with the help of socket programming too. But can someone share their knowledge as to why we should choose ODBC over socket programming for the purpose of connecting to remote databases? In other words, what is/are the advantage(s) of using ODBC over socket programming? I need this information for making a report for an upcoming project. Can anyone help me?
|
|
#2
January 7th, 2004, 09:37 PM
|
|||
|
|||
|
ODBC is high level alternative to programming sockets. You supply the credentials, port and host and the ODBC driver will performing the opening, connecting, management and closing of the connection for you.
Direct socket programming removes this layer of abstraction.
|
|
| Viewing: Dev Shed Forums > Databases > Database Management > Why use ODBC when you can do it through Socket programming? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
