Re^2: AnyEvent for I/O events

The AnyEvent module family grows steadily - AnyEvent::HTTP seems to have hit CPAN just now, and while it isn't as advanced as LWP, it might do what you need. Besides, AnyEvent isn't exclusive as other such "frameworks" - you can mix POE components easily with anyevent modules and code.

Comment on Re^2: AnyEvent for I/O events

Replies are listed 'Best First'.
Re^3: AnyEvent for I/O events by elmex (Friar) on Jun 11, 2008 at 08:15 UTC
There is a whole set of modules now in the AnyEvent suite: AnyEvent::DNS - fully asynchronous DNS resolution AnyEvent::BDB - truly asynchronous berkeley db access AnyEvent::AIO - truly asynchronous file and directrory I/O AnyEvent::DBI - asynchronous DBI access AnyEvent::HTTP - simple but non-blocking HTTP/HTTPS client AnyEvent::FastPing - quickly ping a large number of hosts Modules that also implement protocols are: Net::IRC3 - An event system independend IRC protocol module Net::XMPP2 - An implementation of the XMPP Protocol The great thing is, that you can combine all these protocols and modules in one application or module without threading and without having to choose a specific event loop implementation. I wrote Net::IRC3 and Net::XMPP2, and was really happy I could shift the choice of the event loop to the actual application programmer, who uses my module, making it a lot more useful (This way even the POE or IO::Async world can benefit from my modules).	[reply]

Replies are listed 'Best First'.

Re^3: AnyEvent for I/O events
by elmex (Friar) on Jun 11, 2008 at 08:15 UTC

There is a whole set of modules now in the AnyEvent suite:

AnyEvent::DNS - fully asynchronous DNS resolution
AnyEvent::BDB - truly asynchronous berkeley db access
AnyEvent::AIO - truly asynchronous file and directrory I/O
AnyEvent::DBI - asynchronous DBI access
AnyEvent::HTTP - simple but non-blocking HTTP/HTTPS client
AnyEvent::FastPing - quickly ping a large number of hosts

Modules that also implement protocols are:

Net::IRC3 - An event system independend IRC protocol module
Net::XMPP2 - An implementation of the XMPP Protocol

The great thing is, that you can combine all these protocols and modules in one application or module without threading and without having to choose a specific event loop implementation.

I wrote Net::IRC3 and Net::XMPP2, and was really happy I could shift the choice of the event loop to the actual application programmer, who uses my module, making it a lot more useful (This way even the POE or IO::Async world can benefit from my modules).

[reply]