Skip to content
Commits on Jul 13, 2011
  1. @projectodd-ci
  2. @tobias
Commits on Jul 12, 2011
  1. @tobias
  2. @tobias

    Fix 'application has already been initialized' issues with Rails 3.1 …

    …[TORQUE-477]
    
    We end up calling initialize twice, and rails < 3.1 silently ignores that. 3.1 raises an
    error in that case, which we now silently ignore.
    tobias committed Jul 12, 2011
Commits on Jul 8, 2011
  1. @tobias
  2. @tobias
  3. @tobias
  4. @tobias

    Update to jruby 1.6.3.

    It would be nice if we could figure out the need for jrubyFork, however.
    tobias committed Jul 8, 2011
  5. @tobias

    Backport of future.status=.

    tobias committed Jul 8, 2011
  6. @tobias
Commits on Jul 6, 2011
  1. @tobias

    Small fix to the futures docs.

    tobias committed Jul 6, 2011
  2. @tobias

    This is kind of important.

    tobias committed Jul 6, 2011
  3. @tobias

    Properly handle singleton jobs in a cluster [TORQUE-475]

    This introduces a SchedulerProxy that acts as a go-between for ScheduledJobs
    and the proper Scheduler for that job, since the HASingleton Scheduler will
    not yet exist on a non-master node in a cluster when the job tries to schedule
    itself.
    
    This is a bit of a hack, since we hang the proxy on the ScheduledJobMetaData
    instead of deploying it via the MC.
    tobias committed Jul 6, 2011
Commits on Jun 30, 2011
  1. @jcrossley3
  2. @jcrossley3
Commits on Jun 22, 2011
  1. @tobias

    Revert "Spit out a bit of gem info so we can mayhap see what's up wit…

    …h CI."
    
    This reverts commit f3fc7a0.
    tobias committed Jun 22, 2011
  2. @bobmcwhirter

    Supposed fix for TORQUE-469. When attempting to convert a constant to…

    … a string,
    
    if it's not a constant, just bail, returning the empty string, since, well,
    it's not a constant.
    bobmcwhirter committed Jun 22, 2011
  3. @tobias
Commits on Jun 20, 2011
  1. @tobias
Commits on Jun 16, 2011
  1. @tobias

    Document futures. [TORQUE-450]

    tobias committed Jun 15, 2011
  2. @tobias
  3. @tobias
  4. @tobias
  5. @tobias

    Backgroundables and XTask.async now return future objects [TORQUE-450]

    This adds support for future objects. Asynchronous tasks now return a
    TorqueBox::Messaging::FutureResult, which can be queried via:
    
    * started? - returns true if the processing has started (non-blocking)
    * complete? - returns true if the processing completed w/o error (non-blocking)
    * error? - returns true if the processing raised an error (non-blocking)
    * result(timeout = 0) - returns the result of the completed operation.
      Raises the remote error if an error occurred, and blocks for timeout
      if the processing is not complete. Raises if the timeout expires before
      completion.
    * error - returns the remote error object, if any
    
    TODO: docs
    tobias committed Jun 10, 2011
Commits on Jun 9, 2011
  1. @tobias
  2. @tobias
  3. @jcrossley3 @tobias
Commits on Jun 8, 2011
  1. @tobias
Commits on Jun 7, 2011
  1. @bobmcwhirter
  2. @bobmcwhirter

    more documentation

    Mike Dobozy committed with bobmcwhirter May 25, 2011
  3. @bobmcwhirter

    more documentation

    Mike Dobozy committed with bobmcwhirter May 25, 2011
  4. @bobmcwhirter

    websocket/stomp/stomp-ws support, take 2

    Mike Dobozy committed with bobmcwhirter May 23, 2011
  5. @bobmcwhirter

    Initial stab at websockets/stomp functionality

    Mike Dobozy committed with bobmcwhirter May 10, 2011
  6. @tobias
Commits on Jun 4, 2011
  1. @tobias
Something went wrong with that request. Please try again.