Status update on Network Disconnected

[tbscope]

Depending on the operating system, I don't know.
But my first guess is no, there's no notification when the network cable is unplugged, you need to check that yourself.

Maybe on linux using hal (or its replacement)/dbus/... there might be a way to get a notification.
On Windows, check MSDN for System Notification Services.

You can also try to play with the keep alive option of the socket.

A socket is closed when you explicitly close it. Unplugging the network cable unfortunatly doesn't close the connection, it will just time out. By setting the keep alive value very low, you can minimize the time out. However, this might come with more problems than solutions.

Constantly checkking the status of the network isn't a problem though. It is a correct thing to do. Certainly when you know that the OS, other libraries, ... will most likely do the same but make you add more complexity to your program.
What are your biggest problems with this technique?

[kapoorsudhish]

Depending on the operating system, I don't know.
But my first guess is no, there's no notification when the network cable is unplugged, you need to check that yourself.

Maybe on linux using hal (or its replacement)/dbus/... there might be a way to get a notification.
On Windows, check MSDN for System Notification Services.

You can also try to play with the keep alive option of the socket.

A socket is closed when you explicitly close it. Unplugging the network cable unfortunatly doesn't close the connection, it will just time out. By setting the keep alive value very low, you can minimize the time out. However, this might come with more problems than solutions.
"][/HIGHLIGHT]

Constantly checkking the status of the network isn't a problem though. It is a correct thing to do. Certainly when you know that the OS, other libraries, ... will most likely do the same but make you add more complexity to your program.
What are your biggest problems with this technique?

I am working on Linux platform, adding a thread for polling, is eating up CPU for the UI thread, hence i want a parallel approach which is cleaner than polling from UI.

[tbscope]

Hmm, a timer that checks the network connection every second or so will not consume noticable cpu power.
You don't even need a thread if you don't block the event loop.

[kapoorsudhish]

Thats what i did in the new thread where in

QFuture<void> future = QtConcurrent::run(this,&MyClass::scanNetwork);
 
void MyClass::scanNetwork()
{
   QThread::currentThread()->setPriority(QThread::LowestPriority);
     while(1)
     {
         QNetworkInterface iface (QNetworkInterface::interfaceFromName("eth0"));
         if(iface.isValid())
         {
             if ( iface.flags().testFlag(QNetworkInterface::IsRunning))
             {
                 currentState = Running;
             }
             else
             {
                 currentState = Stopped;
             }
         }
         if(previousState!=currentState)
         {
             previousState=currentState;
             emit (myClass->NetworkCallbackSignal(currentState));
         }
      wait(5000);
     }
}

QFuture<void> future = QtConcurrent::run(this,&MyClass::scanNetwork);

void MyClass::scanNetwork()
{
   QThread::currentThread()->setPriority(QThread::LowestPriority);
     while(1)
     {
         QNetworkInterface iface (QNetworkInterface::interfaceFromName("eth0"));
         if(iface.isValid())
         {
             if ( iface.flags().testFlag(QNetworkInterface::IsRunning))
             {
                 currentState = Running;
             }
             else
             {
                 currentState = Stopped;
             }
         }
         if(previousState!=currentState)
         {
             previousState=currentState;
             emit (myClass->NetworkCallbackSignal(currentState));
         }
      wait(5000);
     }
}

To copy to clipboard, switch view to plain text mode 

I am waiting inside the thread with the low priority for 5 sec then polling again still i have the problem

[squidge]

Get rid of the thread.

Create a class. Use a QTimer. When the timer fires, check the status of the network. If it is different than last time, fire a signal which you app can detect via a slot.