cna you say fuck?

[software/libev.git] / README

diff --git a/README b/README
index e30d7b434e6887f27eb3255c26da85874010837e..de8bb0b119bc67a1910ee52e2a50eb55e1ea121d 100644 (file)
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-libev is a high-performanc3 event loop/event model with lots of features.
+libev is a high-performance event loop/event model with lots of features.

 
 It is modelled (very losely) after libevent
 (http://monkey.org/~provos/libevent/) and the Event perl module, but aims
 
 It is modelled (very losely) after libevent
 (http://monkey.org/~provos/libevent/) and the Event perl module, but aims


@@ -6,7 +6,8 @@ to be faster and more correct, and also more featureful.
 
 DIFFERENCES AND COMPARISON TO LIBEVENT:
 
 
 DIFFERENCES AND COMPARISON TO LIBEVENT:
 

-(comparisons relative to libevent-1.3e and libev-0.00)
+(comparisons relative to libevent-1.3e and libev-0.00, see also the benchmark
+at http://libev.schmorp.de/bench.html).

 
 - multiple watchers can wait for the same event without deregistering others,
   both for file descriptors as well as signals.
 
 - multiple watchers can wait for the same event without deregistering others,
   both for file descriptors as well as signals.


@@ -27,9 +28,6 @@ DIFFERENCES AND COMPARISON TO LIBEVENT:
 - detects time jumps and adjusts timers
   (works for both forward and backward time jumps and also for absolute timers).
 
 - detects time jumps and adjusts timers
   (works for both forward and backward time jumps and also for absolute timers).
 

-- can correctly remove timers while executing callbacks
-  (libevent doesn't handle this reliably and can crash).
-

 - race-free signal processing
   (libevent may delay processing signals till after the next event).
 
 - race-free signal processing
   (libevent may delay processing signals till after the next event).
 


@@ -66,13 +64,15 @@ DIFFERENCES AND COMPARISON TO LIBEVENT:
 - a event.h compatibility header exists, and can be used to run a wide
   range of libevent programs unchanged (such as evdns.c).
 
 - a event.h compatibility header exists, and can be used to run a wide
   range of libevent programs unchanged (such as evdns.c).
 

-whats missing?
+- win32 compatibility for the core parts.

 
 

-- evbuffer, evhttp, bufferevent are missing.
+- the event core library (ev and event layer) compiles and works both as
+  C and C++.

 
 

-- no priority support at the moment (but likely to be delivered later).
+whats missing?

 
 

-- kqueue, poll (libev currently implements epoll and select).
+- no event-like priority support at the moment (the ev priorities
+  are not yet finished and work differently, but you cna use idle watchers
+  to get a similar effect).

 
 

-- windows support (whats windows?).