handle +package

package HandlerSocketClient
package
This package implemets API for a HandlerSocket client. Version 0.0.5
package bytestring-handle
package
package event-handlers
package
Simple event handler set management. Version 0.0.0.3
package hack-handler-cgi
package
package hack-handler-epoll
package
Hack handler implemented using System.Linux.Epoll Version 0.1.3
package hack-handler-evhttp
package
Hack EvHTTP (libevent) Handler Version 2009.8.4
package hack-handler-fastcgi
package
package hack-handler-happstack
package
Hack Happstack server handler Version 2009.12.20
package hack-handler-hyena
package
Hyena hack handler Version 2010.3.15
package hack-handler-kibro
package
Hack Kibro handler Version 2009.5.27
package hack-handler-simpleserver
package
This should not be used in a production environment. However, it's useful for testing. 0.2.0.2 is equal to 0.2.0.1 but with extended ranges for network and web-encodings packages Version 0.2.2
package hack2-handler-happstack-server
package
Hack2 Happstack server handler Version 2011.6.20
package hack2-handler-mongrel2-http
package
Hack2 Mongrel2 HTTP handler Version 2011.10.31
package hack2-handler-snap-server
package
Hack2 Snap server handler Version 2012.1.19
package hack2-handler-warp
package
Hack2 warp handler Version 2012.5.25
package mongrel2-handler
package
Mongrel2 Handler Library. This handler library requires that the Mongrel2 server is set up to use the tnetstring protocol. Version 0.3.2
package redHandlers
package
Monadic HTTP request handlers combinators to build a standalone web apps. Most of them deal with request data. Some of them allow mapping part of the URL to public folders in the file system. There is also a combinator for sending files efficiently in the response (a fork of the HTTP library was necessary for this, included here). Version 0.1
package safer-file-handles
package
This package adds three safety features on top of the regular System.IO file handles and operations: * Regional file handles. Files must be opened in a region. When the region terminates all opened files are automatically closed. The main advantage of regions is that the handles to the opened files can not be returned from the region which ensures no I/O with closed files is possible. * Explicit IOModes. The regional file handles are parameterized by the IOMode in which they were opened. All operations on handles explicitly specify the needed IOMode. This way it is impossible to read from a write-only handle or write to a read-only handle for example. * Type-safe filepath creation and manipulation using the pathtype package. The primary technique used in this package is called "Lightweight monadic regions" which was invented by Oleg Kiselyov and Chung-chieh Shan. See: http://okmij.org/ftp/Haskell/regions.html#light-weight This technique is implemented in the regions package which is re-exported from safer-file-handles. See the safer-file-handles-examples package for examples how to use this package: git clone https://github.com/basvandijk/safer-file-handles-examples See the safer-file-handles-bytestring/text package for ByteString/Text operations on regional file handles. Version 0.11
package safer-file-handles-bytestring
package
Extends safer-file-handles with ByteString operations Version 0.3.0.1
package safer-file-handles-text
package
Extends safer-file-handles with Text operations Version 0.2.0.2

Show more results