On Fri, May 20, 2011 at 01:11:49PM +0300, Torste Aikio <[email protected]> wrote:
> I'm trying to use raw sockets with libev, but have a problem getting
> READ events firing.
I would expect read events to fire, e.g. when the socket becomes readable
- the question is, why is that a problem?
In general, libev doesn't know anything about sockets, it only passes what
the kernel thinks to your app. If you have differences between raw sockets
and udp sockets, then most likely this is because the kernel treats them
differently (for example, due to the error queue or sth. like that).
Without knowing what you think the problem is, I can't give you a more
definite answer.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
libev mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
