Hi Alex,
>I just started playing with Haskell for CGI applications.
>I would like to try writing a more serious CGI app, but
>missing infrastructure makes it more difficult than conventional
>approaches.
>
>In decreasing order of preference, is there an available implementation of:
>* an equivalent to Java's Naming and Directory Services interface
>* an LDAP client for some particular LDAP server
If you don't mind to restrict yourself to Windows, and these applications
are available as COM Automation objects you
are done. We already interfaced to the ADSI components,
would that be enough?
In theory we can interoperate with any plain COM component, but
the technology for that is not yet stable. And as Alastair pointed
out GreenCard can be used to interface to plain C libraries.
>* an XML editor
Perhaps you mean an XML parser/unparser. The MS XML parser
is an Automation object, so it can be scripted from Haskell. Implementing
a full XML parser and pretty-printer in Haskell is not hard. A generic XML
parser that ignores the DTD but parses any well-nested document can
be programmed using a few lines of parser combinators.
>* a generic ODBC/JDBC database client
>* an interface to berkeleyDB (or some persistent hashtable implementation)
This is high on our list too.
>I suppose that I could have Haskell talk to Jacl to access the Java
>implementations of these capabilities, but this seems like a hack.
>
>Any pointers?
Hop this helps, if you need more specifc information don't hesitate
to contact me.
To answer Tommy:
> I think there are two major causes to this effect: one is the high
> emphasize on theoretical aspects of the language and a disproportional
> low effort on plain practial aspects.
I agree, if only I had the resources!
Erik
