Seems that I've got the hang of complaining about libraries :)
While working I noticed two things in there:
1) Using Socket.accept, it's not possible to find out the port-number the
remote end is using. You have to work around this using SocketPrim.accept,
though I consider this rather useful/important.
How about changing Socket.accept from returning (Handle,Hostname) to
(Handle,(Hostname,Port))? Although this would mean you'd all have to touch
your sources which use this, I think it's worth doing this before everyone using
sockets starts tweaking their own stuff. Recent messages posted to the list
seem to show that more and more people are actually using this Haskell-stuff.
2) Is anyone actually using Socket.recvFrom? It must have been written for
*some* purpose, but I can't see any earthly use [okay, I could if I'd want to,
but this function is rather too specialised for a network-interface toolkit].
I hope I'm not treading too many toes of the people who had to build the
interfaces..
Volker
--
Volker Stolz * [EMAIL PROTECTED] * PGP
