Difference between revisions of "Real World Applications"

From HaskellWiki
Jump to: navigation, search
(First page)
 
m (Improved layout)
Line 9: Line 9:
 
An event driven application is an application that reacts to external events.
 
An event driven application is an application that reacts to external events.
  
Examples would be a text editor that reacts to user events (key pressed, mouse moved), a web server reacting to IO events (message arrived, image compression done) and a commercial game reacting to simulated physics events and user input.
+
Examples would be:
 +
 
 +
* A text editor that reacts to user events (key pressed, mouse moved).
 +
* A web server reacting to IO events (message arrived, image compression done).
 +
* A commercial game reacting to simulated physics events and user input.
  
 
[[/Event_Driven_Applications/] Event Driven Applications]
 
[[/Event_Driven_Applications/] Event Driven Applications]

Revision as of 11:05, 2 July 2014

Introduction

It is not always clear how to scale up from small "batch oriented" Haskell applications to large scale "Real World"/"Enterprise" Haskell systems.

The following articles discuss different ways to attack this problem.

Event Driven Applications

An event driven application is an application that reacts to external events.

Examples would be:

  • A text editor that reacts to user events (key pressed, mouse moved).
  • A web server reacting to IO events (message arrived, image compression done).
  • A commercial game reacting to simulated physics events and user input.

[[/Event_Driven_Applications/] Event Driven Applications]

?

Please contribute additional/alternative ways to structure large scale Haskell applications here!

Questions and feedback

If you have any questions or suggestions, feel free to mail me.