Permalink
Commits on May 8, 2016
  1. Release as version 0.6.5

    committed May 8, 2016
  2. Bump version.

    committed May 8, 2016
  3. Update .gitlab-ci.yml

    committed May 8, 2016
  4. Add .gitlab-ci.yml

    committed May 8, 2016
  5. Add lower bounds.

    committed May 8, 2016
Commits on May 5, 2016
Commits on Jan 5, 2016
  1. Merge branch 'develop'

    committed Jan 5, 2016
  2. Update async dependency.

    committed Jan 5, 2016
Commits on Mar 28, 2015
  1. Fix GHC 7.10.1 warnings

    committed Mar 28, 2015
Commits on Feb 13, 2015
  1. Release as version 0.6.3

    committed Feb 13, 2015
  2. Update CHANGELOG

    committed Feb 13, 2015
Commits on Feb 12, 2015
  1. Allow exceptions 0.7

    committed Feb 12, 2015
Commits on Jan 7, 2015
  1. Merge pull request #62 from k0ral/master

    Added Typeable instance for Context
    committed Jan 7, 2015
Commits on Jan 4, 2015
Commits on Dec 22, 2014
  1. Compile against 0MQ 4.1 RC.

    committed Dec 22, 2014
Commits on Dec 14, 2014
  1. Expose internal modules.

    committed Dec 14, 2014
Commits on Sep 25, 2014
  1. Merge branch 'issue-56'

    committed Sep 25, 2014
Commits on Sep 13, 2014
  1. Issue#56: Add `messageFree` and use it in send.

    man zmq_msg_close (3) states:
    
        Applications should ensure that zmq_msg_close() is called
        once a message is no longer required, otherwise memory
        leaks may occur. Note that this is NOT necessary after a
        successful zmq_msg_send().
    
    Usually when 0MQ closes the message implictly it re-initialises it as
    well. Sometimes this doesn't happen though (cf. [1]) so it is possibly
    the best strategy to only free the pointer on our end.
    
    ---
    [1] zeromq/libzmq#721
    committed Sep 13, 2014
Commits on Aug 29, 2014
Commits on Aug 16, 2014
  1. Issue #55: Restructure wait loop.

    The current implementation of `wait'` first retrieves the socket's
    file descriptor and uses GHC's `threadWaitRead` and `threadWaitWrite`
    to wait. Then it checks the 0MQ socket events if writing or reading
    could be done in a non-blocking way.
    
    AFAICS the file descriptor should only be polled for read events, as it
    most likely isn't the actual FD where data is sent through. This aligns
    with what api.zeromq.org states:
    
      "[...] the ØMQ library shall signal any pending events on the socket
      in an edge-triggered fashion by making the file descriptor become
      ready for reading." [1]
    
    The behaviour described in #55 is caused by using `threadWaitWrite` on
    this FD which immediately returns, but asking for `ZMQ_POLLOUT` events
    is answered negatively as no clients have connected. Hence the loop is
    restarted ad infinitum.
    
    A related issue is the edge-triggered fashion in which the FD is
    signaled. Currently we might wait longer than necessary for subsequent
    messages as we always wait on the file descriptor first which would be
    correct for level triggering.
    
    This commit changes the behaviour in that we always inspect the 0MQ
    socket events first. If they match with what has been requested we
    directly continue writing or reading. Only if this test fails do we wait
    with `threadWaitRead` for the underlying FD to become ready.
    
    ---
    [1] http://api.zeromq.org/4-0:zmq-getsockopt#toc24
    committed Aug 16, 2014
Commits on May 21, 2014
  1. Fix compatibility with previous GHC versions

    Modify cabal file to include ghc-prim in build-depends when
    GHC version is smaller than 7.6.
    
    Signed-off-by: Spyros Trigazis <strigazi@gmail.com>
    strigazi committed May 21, 2014
Commits on May 6, 2014
  1. Update CHANGELOG

    committed May 6, 2014
Commits on Apr 15, 2014
  1. Add CHANGELOG

    committed Apr 15, 2014
Commits on Apr 10, 2014
  1. Fix typos.

    committed Apr 10, 2014
  2. Small refactoring.

    committed Apr 10, 2014
  3. Merge pull request #47 from qnikst/fix-last-endpoint

    Fix incorrect reading of a string options.
    committed Apr 10, 2014
  4. Merge pull request #46 from qnikst/export-socket-monitor

    Expose socketMonitor call.
    committed Apr 10, 2014