diff options
author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2013-05-07 21:58:34 -0500 |
---|---|---|
committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2013-05-07 21:58:34 -0500 |
commit | c740211ffba3330d951f4c3ddefea8edf23a01cd (patch) | |
tree | 0a8b7641d3c5b576d18a2f7912c75fc600f494e2 /doc/networking.doc | |
parent | 8a4eacb6185de3653f6ae401c352aef833a9e72a (diff) | |
download | tqt3-c740211ffba3330d951f4c3ddefea8edf23a01cd.tar.gz tqt3-c740211ffba3330d951f4c3ddefea8edf23a01cd.zip |
Automated update from Qt3
Diffstat (limited to 'doc/networking.doc')
-rw-r--r-- | doc/networking.doc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/networking.doc b/doc/networking.doc index 62b4a49a..41db5cf8 100644 --- a/doc/networking.doc +++ b/doc/networking.doc @@ -275,7 +275,7 @@ Protocol) is declared (\c network/infoprotocol/infourlclient/qip.h): \skipto Qip \printuntil }; -QNetworkProtocol is the base class for every Network Protocol class. Because this protocol uses network, we embedded one QSocket* member variable to which we'll delegate network communication. Protocols that doesn't require to use network will do it on their own way - e.g. QLocalFs uses QDir, some data actquisition protocol may use serial or USB connection, only requirement is that protocol uses hierarchical structure and can be accessed using URLs (to have addressable nodes). +QNetworkProtocol is the base class for every Network Protocol class. Because this protocol uses network, we embedded one QSocket* member variable to which we'll delegate network communication. Protocols that doesn't require to use network will do it on their own way - e.g. QLocalFs uses QDir, some data acquisition protocol may use serial or USB connection, only requirement is that protocol uses hierarchical structure and can be accessed using URLs (to have addressable nodes). Let us go to the Qip implementation (\c network/infoprotocol/infourlclient/qip.cpp): @@ -346,7 +346,7 @@ Here is where we use some QNetworkProtocol magic. (QUrlOperator)op is constructe \printuntil return \printuntil } -This function implements simple QFileDialog that will serve us to browse through the nodes on the server and to select one data node to view. Starting url is "qip://localhost/" which indicates to QFileDialog that we want to use Qip protocol served on the local server. We could also specify the exact port, e.g. "qip://my_server:123" will try to intquire my_server over port 123, otherwise the default port is used. +This function implements simple QFileDialog that will serve us to browse through the nodes on the server and to select one data node to view. Starting url is "qip://localhost/" which indicates to QFileDialog that we want to use Qip protocol served on the local server. We could also specify the exact port, e.g. "qip://my_server:123" will try to inquire my_server over port 123, otherwise the default port is used. We didn't use static function QFileDialog::getOpenFileName() because under Windows and Mac OS X, it will usually use the native file dialog and not a QFileDialog, in which case we wouldn't be able to use our protocol at all. |