On Mon, Jun 23, 2014 at 6:39 PM, Henrik Nordström <hen...@henriknordstrom.net> wrote: > tis 2014-06-24 klockan 02:21 +0200 skrev Henrik Nordström: > >> Not that I can see. You need to try to perform read/write on each active >> channel & stream to see if there is anything to perform whenever the >> session fd is active in epoll. > > Thinking on this. Would it make sense to have an API to query what the > next packet in the receive queue is about? This would allow > multi-channel applications to scale better with number of channels by > avoiding to repeatedly loop over all channels (&streams) whenever there > is any activity. >
in response to last two emails (there is one missing in my inbox): - if we could determinate the type of packet would be awesome. - the number of channels to handle may vary between 10 and 20. I do not worry too much about performance at this point. just to clarify, whats the real difference between a channel and a stream in libssh2 ? thanks, _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
