I would point you towards the "other" event oriented protocols, like irc clients. They and the protocol lend themselves well towards event oriented approaches. But they are quite similar to webservers in their nature anyway.
Maybe all systems where events come in and get dispatched are such a class? Although I see the advantage if you have multiple clients and more complex interactions than request -> response, where the linear flow in programming is preferrable over the event oriented approach, where you stitch together the flow by keeping some additional state.
In reply to Re^6: Doing an Input->process->Output cycle with AnyEvent? (was: error: "recursive blocking wait detected")
by Corion
in thread Doing an Input->process->Output cycle with AnyEvent? (was: error: "recursive blocking wait detected")
by isync
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |