Don't get me wrong -- the socket support is pretty decent, but there are also
some weird idiosyncrasies, for example requiring that the PortNum is
specified in network byte order and lacking a function to convert
host-network byte order (hton).
PortNum is indeed strange, but it does allow yo
On 2009 Jan 9, at 20:51, Tim Newsham wrote:
I'm suprised htonl comes up so often. You can unmarshall data
directly from a byte stream to an Int type without caring about the
underlying representation of your Int. Why do people want the htonl
function?
IP address math. (see @ipcalc in
On 2009-01-08 12:10, Achim Schneider wrote:
Manlio Perillomanlio_peri...@libero.it wrote:
Unfortunately Haskell is not yet ready for this task.
Could you -- or someone else -- please elaborate on this?
I think Haskell is ready for a lot more than most people think. How about an
operating
John A. De Goes wrote:
Here's hoping someone develops a native messaging framework for Haskell,
which is the equal of RabbitMQ.
The first thing would be to make a Haskell client library to speak AMQP
(Advanced Message Queuing Protocol) on the wire.
It is a very open binary standard
Manlio Perillo wrote:
John Goerzen ha scritto:
On Thu, Jan 08, 2009 at 10:36:32AM -0700, John A. De Goes wrote:
[...]
On the other hand, I see nothing in Haskell that would prevent its use
for any of your purposes. There are numerous high-level web
infrastructures already. Perhaps they are
PortNum is specified in network byte order and lacking a function to
convert host-network byte order (hton).
Perhaps this is another argument for my thread from a while back?
http://www.nabble.com/Missing-Network-Functions-td21188779.html
/jve
On Thu, Jan 8, 2009 at 4:37 PM, Bardur Arantsson
On Thu, Jan 08, 2009 at 10:37:55PM +0100, Bardur Arantsson wrote:
Don't get me wrong -- the socket support is pretty decent, but there are
also some weird idiosyncrasies, for example requiring that the PortNum
is specified in network byte order and lacking a function to convert
John Goerzen wrote:
On Thu, Jan 08, 2009 at 10:37:55PM +0100, Bardur Arantsson wrote:
Don't get me wrong -- the socket support is pretty decent, but there are
also some weird idiosyncrasies, for example requiring that the PortNum
is specified in network byte order and lacking a function to
On Thu, 8 Jan 2009, Bardur Arantsson wrote:
Thanks. For some reason I hadn't thought to use
(fromIntegral x)::PortNumber
I guess I got stuck on the idea of constructing a PortNum directly and didn't
think beyond that. (Maybe PortNum should really be an abstract type to force
indirect
Bardur Arantsson wrote:
Thanks. For some reason I hadn't thought to use
(fromIntegral x)::PortNumber
I guess I got stuck on the idea of constructing a PortNum directly and
didn't think beyond that. (Maybe PortNum should really be an abstract
No problem. I knew exactly what your
10 matches
Mail list logo
