1 Missing libraries (by problem domain)

1.1 IMAP

A functional IMAP library would be nice, particularly one that can be used in conjunction with encryption and authentication. References have been found to a SoC project although it appears to be derelict.

1.2 Numerical algorithms

Stuff to compute bessel functions, struve H1 etc.

1.3 .NET/Java Interoperability

We could use a .NET FFI library that lets you easily call into the .NET framework. Perhaps the (abandoned?) Hugs .NET FFI library could be resurrected/updated and ported to GHC? Maybe a tool could even be created that automates the interoperability of Haskell and arbitrary .NET libraries?

I'm working on a Haskell to .NET bridge for my undergraduate thesis. The goal is to provide access to arbitrary .NET libraries from Haskell, with a convenient syntax. I expect to have something releasable in a few weeks. AndrewA 13:33, 6 October 2007 (UTC)

1.4 AMQP Client

It will be great to have a client for the open source protocol AMQ (http://en.wikipedia.org/wiki/Advanced_Message_Queuing_Protocol). This is a new transport protocol, solving problems currently addressed by Java Messaging Service, MQ, Tibco RV, etc. Financial companies such infrastructure to distribute massive amounts of market data (although the protocol can be used for effeciently distributing anything)

1.5 STOMP Client

The Streaming Text Orientated Messaging Protocol (http://stomp.codehaus.org/) is a messaging protocol supported by a good number of languages and message brokers. While not high-performance like AMQP it is apparently near trivial to implement and interact with.

1.6 Darcs Bindings

Many darcs users have requested an interface to darcs as a C library. Creating this library would involve deciding on the details of the API and generating the bindings using the Haskell FFI. Designing the API is mostly done for you by following the structure of the darcs source code and how the existing commands interface with the core of darcs.

1.7 OpenID Relying Party (Consumer) library

A library allowing (web) applications to authenticate users with an OpenID would be great. WikiPedia has a good description of what is expected from the relying party.

2 Could be improved

Problems with existing solutions, that could be improved.

The core HTTP libraries need a lot of work. There is the beginnings of a useful library there, but many http codes are not handled, and there should be simple 'get' and 'head' functionality.

Binary serialisation support should be ported to bytestring, and added to the extralibs bundle