Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Apr 26, 2012
  1. @slyphon

    bump to next version

    slyphon authored
  2. @slyphon
  3. @slyphon

    ruby 1.8.7, i hate you

    slyphon authored
  4. @slyphon

    gah, clean state before run

    slyphon authored
  5. @slyphon

    bump version to 0.9.1

    slyphon authored
  6. @slyphon
  7. @slyphon

    cruft removal

    slyphon authored
  8. @slyphon

    Fix a fairly bad bug in event de-duplication

    slyphon authored
    This is fairly edge-case-y but could bite someone. If you'd set a watch
    when doing a get that failed because the node didn't exist, any subsequent
    attempts to set a watch would fail silently, because the client thought that the
    watch had already been set.
    
    We now wrap the operation in the setup_watcher! method, which rolls back the
    record-keeping of what watches have already been set for what nodes if an
    exception is raised.
    
    This change has the side-effect that certain operations (get,stat,exists?,children)
    will block event delivery until completion, because they need to have a consistent
    idea about what events are pending, and which have been delivered. This also means
    that calling these methods represent a synchronization point between user threads
    (these operations can only occur serially, not simultaneously).
Commits on Apr 24, 2012
  1. @slyphon
  2. @slyphon
  3. @slyphon
  4. @slyphon

    complain VERY LOUDLY if close! is called on the event dispatch thread…

    slyphon authored
    …, but do not deadlock
    
    Rather than deadlocking and causing problems, we will vomit with an error and
    print a Kernel.warn message so *hopefully* the user will see one of those and
    realize they've done something wrong.
    
    The only alternative at this point would be to call exit! which would be
    unconscionably horrendous, or some hack that would raise an exception (at random)
    in the main thread (which would be dangerous and stupid).
  5. @slyphon
  6. @slyphon
  7. @slyphon

    Default logger now logs to $stderr with ERROR level only.

    slyphon authored
    This change is so that errors in user-supplied callbacks will be logged
    *somewhere* possibly visible to the user.
  8. @slyphon
  9. @slyphon
Commits on Apr 23, 2012
  1. @slyphon

    informal test for forking

    slyphon authored
  2. @slyphon

    bump version

    slyphon authored
  3. @slyphon
  4. @slyphon
  5. @slyphon
  6. @slyphon
  7. @slyphon

    a note-to-self about what kinds of events the event handler handles

    slyphon authored
    (if the event handler could handle events)
  8. @slyphon
  9. @slyphon
Commits on Apr 22, 2012
  1. @slyphon

    ok, so, funny story, that threaded client change *totally* deadlocks …

    slyphon authored
    …a lot of stuff, revert it
  2. @slyphon

    yeah, this doesn't go here

    slyphon authored
  3. @slyphon
  4. @slyphon

    block_until_node_delete should never be called on the event delivery …

    slyphon authored
    …thread
    
    this would cause events to never get delivered ever again, and the client
    might never be aware of the condition (until they realize no events are
    getting delivered)
    
    with specs
  5. @slyphon
  6. @slyphon

    change base class methods to use cnx attr_reader

    slyphon authored
    this will allow us to do things like synchronize access in the threaded client
  7. @slyphon

    rename spec

    slyphon authored
  8. @slyphon
  9. @slyphon

    fix namespacing, include ZK::Exceptions::InterruptedException in rele…

    slyphon authored
    …vant underlying exceptions
Something went wrong with that request. Please try again.