alex wrote:Currently, there is only select() (or poll(), where available) for sockets.
Does this mean, the handling is integrated (hard coded) into this part of the class tree?
alex wrote:I did start some work on the functionality you are looking for, but it is not available to the public yet (and I can make no timeframe promises).
Which approach do you use? Do you plan a single dispatcher like the loop/dispatch functions of C-Libaries like libevent or libev?
alex wrote: If you would be interested in contributing, email me at(alex, dot(appinf, us))
That would be possible. I'm developing embedded systems most of the time. In most cases I use C, but with ARM-based cores, the usage of C++ is getting more. I've written a few (portable) desktop applications with fltk (http://www.fltk.org
). POCO is on my todo list for a long time now, but I had not have the time to start with it.
Nevertheless, if you have some code to get a first impression, I will have a look at it. I'll send you an email...
By the way... Can you point me to some samples or papers to get a better overview over the class hierarchy and the design principles of POCO? The reference is flat and too large.
And one more question... Why don't you support pkg-config? I'm using debian linux, and the official poco packages neither have support for pkg-config, nor are the POCO makefile rules included.