Which set of classes should I use for my app?

[Sylva1n]

Hello,

I have just discovered the POCO world and I'm a bit lost.

I plan to code an app which has to:

• be launched as a deamon
• launch several threads

• Two of those threads listens to a port through a socket (TCP).
• Another thread has to send multicast datagrams (UDP).
• The last two threads have to run processes (like grep or wget) and retrieve the processes output.
• The main thread should safely communicate with those threads and vice-versa

Between ServerApplication, SocketReactor and SocketNotification (cf. EchoServer.cpp example), NotificationQueue (cf. NotificationQueue.cpp example) and TaskManager (cf. SampleServer.cpp example), I don't know which design to choose according to my app functionalities.

May you give me some advice?

best regards,

Sylvain

[alex]

[*]be launched as a deamon

Poco::Util::ServerApllication

launch several threads

Poco::Thread (maybe also Poco::ThreadPool)

Two of those threads listens to a port through a socket (TCP).

Poco::Net::ServerSocket
EDIT: you may also consider Poco::Net::TCPServer, which is already threaded and uses ThreadPool.

Another thread has to send multicast datagrams (UDP).

Poco::Net::DatagramSocket

The last two threads have to run processes (like grep or wget) and retrieve the processes output.

Poco::Process

The main thread should safely communicate with those threads and vice-versa

Poco::NotificationQueue

Between ServerApplication, SocketReactor and SocketNotification (cf. EchoServer.cpp example), NotificationQueue (cf. NotificationQueue.cpp example) and TaskManager (cf. SampleServer.cpp example), I don't know which design to choose according to my app functionalities.

Reactor is basically a select() (or poll()/epoll(), where available) loop with notifications, so anything related to sockets above can be done with Reactor, it's just a different model from threads plus blocking .

HTH

Alex